Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GH-4817 LMDB: Make close method of LmdbRecordIterator thread-safe. #4818

Merged
merged 1 commit into from
Nov 7, 2023

Conversation

kenwenzel
Copy link
Contributor

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):

  • my pull request is self-contained
  • I've added tests for the changes I made
  • I've applied code formatting (you can use mvn process-resources to format from the command line)
  • I've squashed my commits where necessary
  • every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change

…read-safe.

Ensures that a lock is used if close() is called asynchronously
from another thread than next().
@kenwenzel
Copy link
Contributor Author

@hmottestad Is it expected that the Elasticsearch test fails?

@hmottestad
Copy link
Contributor

They have been failing a lot lately. I think that those tests use the elasticsearch testing harness that is internal to Elastic and not meant for public usage. I don't really know what has changed to make them start failing now though.

@hmottestad
Copy link
Contributor

I'm rerunning it now to see if it passes the second time around. That's been my experience at least.

@hmottestad
Copy link
Contributor

Could be because I've updated the surefire and failsafe maven plugins.

@hmottestad hmottestad merged commit 00e6099 into eclipse-rdf4j:main Nov 7, 2023
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

LMDB: Make close method of LmdbRecordIterator thread-safe
2 participants