-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Construct query creating RDFstar statements in memory store does not work anymore with RDF4J 4.1 #4112
Comments
hmottestad
added a commit
that referenced
this issue
Aug 17, 2022
…at we don't accidently share one Var object between multiple tuple expressions
hmottestad
added a commit
that referenced
this issue
Aug 17, 2022
hmottestad
added a commit
that referenced
this issue
Aug 17, 2022
5 tasks
hmottestad
added a commit
that referenced
this issue
Aug 17, 2022
hmottestad
added a commit
that referenced
this issue
Aug 18, 2022
hmottestad
added a commit
that referenced
this issue
Aug 18, 2022
GH-4112 fix query regression for CONSTRUCT query with RDF*
Thanks for fixing this, @hmottestad! |
We do not have a planned date yet. |
@jetztgradnet I've just now released 4.1.1. |
@hmottestad thanks for the notification (and the bugfix!), we'll update shortly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Behavior
Running a
CONSTRUCT
query in a memory store fails to create RDFstar statements with RDF4J 4.1 with the following error:The example query:
This worked previously with RDF4J 4.0. Removing the 3 lines creating RDFstar statements in the
CONSTRUCT
clause also makes it work with 4.1, but it doesn't accept the RDFstar patterns, not even the "static" one (last one in the example above) without any variables.This query works fine with current versions of GraphDB (9.x and 10) and Stardog.
Parsing the query fails with this stacktrace:
Expected Behavior
Being able to create RDFstar statements in a
CONSTRUCT
query.Steps To Reproduce
Version
4.1.0
Are you interested in contributing a solution yourself?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: