Iteration: Getting SPARQL-parser in loket #695
Draft
Conversation
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.
This is another iteration of getting
sparql-parserin loket.This contains:
A workaround for a virtuoso bug. Updated the sparql-parser config.
Disable the (full) caching system for mu-resource. Sparql-parser generates too much deltas for mu-resource to be able to handle these. Probably this won't even be noticed, given the speed up sparql-parser gives
TODO: figure out if the special build of mu-resource is still needed, given we don't use it's caching system anymore
There is a (yet to be confirmed) bug, about same 'rdf:type' in multiple graphs. Waiting for feedback here.
See also: https://binnenland.atlassian.net/browse/DL-7020