GH-4817 LMDB: Make close method of LmdbRecordIterator thread-safe. #4818
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ensures that a lock is used if close() is called asynchronously from another thread than next().
GitHub issue resolved: #4817
Briefly describe the changes proposed in this PR:
Ensures that close method does not interfere next if called asynchronously from another thread.
PR Author Checklist (see the contributor guidelines for more details):
mvn process-resources
to format from the command line)