Use RDF4J native store in place of Blazegraph#583
Draft
Conversation
Member
Author
|
Related to geneontology/project-management#69 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Blazegraph is no longer developed, and is dependent on a very old version of RDF4J (i.e., Sesame) which isn't compatible with modern OWL API.
This PR switches the backing triplestore to use the built-in native store in the latest RDF4J release. It will require Java 11.
So far, migrated application to use RDF4j native store, and seems to work well for the most part.
Load performance on my laptop:
Dumping all models to turtle took 2.5 minutes.
Known issues: