Skip to content

Use RDF4J native store in place of Blazegraph#583

Draft
balhoff wants to merge 1 commit intomasterfrom
native-store
Draft

Use RDF4J native store in place of Blazegraph#583
balhoff wants to merge 1 commit intomasterfrom
native-store

Conversation

@balhoff
Copy link
Copy Markdown
Member

@balhoff balhoff commented Jan 24, 2026

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:

2026-01-24 11:22:35,519 INFO  (org.geneontology.minerva.BlazegraphMolecularModelManager:615) Done loading gocams, loaded: 54474 out of: 54985 files

real 6m6.833s
user 5m9.612s
sys  0m43.450s

Dumping all models to turtle took 2.5 minutes.

Known issues:

  • Tests still require updating to handle places where a Blazegraph journal is downloaded and used.
  • OWL API 4 uses an older version of RDF4J (3.x), while only OWL API 5 uses RDF4J 5. There are some problems with the Turtle RIO parser as a result. (I have an update PR to OWL API 4: Align version4 with RDF4J version used in version5 owlcs/owlapi#1170)
  • Need to review all SPARQL queries into the ontology to check performance.

@balhoff
Copy link
Copy Markdown
Member Author

balhoff commented Feb 20, 2026

Related to geneontology/project-management#69

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.

1 participant