RDF4J: disable checking by default, allow enabling via factory setting#549
Merged
Karolina-Bogacka merged 2 commits intomainfrom Sep 28, 2025
Merged
RDF4J: disable checking by default, allow enabling via factory setting#549Karolina-Bogacka merged 2 commits intomainfrom
Karolina-Bogacka merged 2 commits intomainfrom
Conversation
Unfortunately, the term validation stack in RDF4J is very heavy, and with it the Jelly parser become 2–4x slower. I think it makes more sense to disable all the checks by default. To make it possible to enable these checks in RDF4J parser consistency tests, I also added a setting on the parser factory itself, to control whether parser instances produced by it will be checking or not.
Codecov Report✅ All modified and coverable lines are covered by tests.
... and 2 files with indirect coverage changes 🚀 New features to boost your workflow:
|
Karolina-Bogacka
approved these changes
Sep 28, 2025
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
2 participants
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.
Unfortunately, the term validation stack in RDF4J is very heavy, and with it the Jelly parser become 2–4x slower. I think it makes more sense to disable all the checks by default.
To make it possible to enable these checks in RDF4J parser consistency tests, I also added a setting on the parser factory itself, to control whether parser instances produced by it will be checking or not.