Fixed the NPE bug to support the SPARQL str function, and throw NotImplementedException for comparing subject variable value #408
Conversation
This file contains 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
…plementedException for comparing subject variable value.
awoods
pushed a commit
that referenced
this pull request
Jul 8, 2014
Fixed the NPE bug to support the SPARQL str function, and throw NotImplementedException for comparing subject variable value
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.
https://www.pivotaltracker.com/s/projects/684825/stories/71073904
I think I've fixed the NPE bug and added the str() function support for filter queries. However, the filter query will work for literal values only but not subject reference, and I've let it thrown the NotImplementedException when a SPARQL is trying to compare subject reference as literal values.