SPARQLParser().parseQuery(String queryStr, Sring baseURI) no longer returns the ParsedQuery with ProjectionElem Aliases? #4904
Unanswered
ABLEquitus
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dear RDF4J community,
I would like to preface this by thanking all of you in advance for your contributions and potential assistance.
I am working on my own fork of Apache Rya. I have been refactoring to update various dependencies. The original version of RDF4J used in the aforementioned mirror is 2.3.1. The transition from RDF4J major version 2 to 3 was pretty straightforward, but I am having a bit of trouble with transition from RDF4J major version 3 to 4.
The version of RDF4J that I am using now is 4.3.9 and when running some tests (ProjectionEvaluatorTest, ProjectionProcessorTest), the tests related to renaming bindings fail. For reference, the original source code for these tests is located here.
Here is the renameBindings() test from the ProjectionEvaluatorTest class:
and here is the getProjection(String sparql) method:
This is the output of the test:
While doing some debugging with IntelliJ IDEA, it seems that the projection aliases are lost after line 163 of SPARQLParser:
TupleExpr tupleExpr = this.buildQueryModel(qc);
and the resulting tupleExpr is:
whereas, in previous versions of RDF4J, the result of the same operation yields this tupleExpr which retains the aliases:
Any suggestions would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions