Documentation fix?

While performing some testing on Streams in Repositories i.e.

Stream<Thing> findAllBySomething();

I came up against the max scroll Context error refered to in #406 and #1337 Trying to create too many scroll contexts. Must be less than or equal to: [500]

At the bottom of Section 11.2 the following is stated

If the Stream is not closed and you are able to create 500 scroll contexts within the 60 seconds it triggers the exception.

I wondered if it was worth explaining that a try-with-resources should be used to make sure the Stream was closed and therefore the scroll context?

[sothawo]

Implemented with #1746, now you don’t have to call close, this is done automatically. Thanks for finding this.

[sothawo]

Fair point with the hint that most streams do not require a close operation and it should be documented.

But instead of adding this behaviour to the docs I will better change the implementation that reads the data from Elasticsearch to automatically close the scroll context when all results are returned so that an explicit close is not necessary.

I created #1745 for this, will do it later today.