[
https://issues.apache.org/jira/browse/JENA-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735357#comment-13735357
]
Hudson commented on JENA-500:
-----------------------------
SUCCESS: Integrated in Jena_Development_Test #828 (See
[https://builds.apache.org/job/Jena_Development_Test/828/])
Additional test for JENA-500 just to validate that initial bindings by
substitution doesn't break when using the variable whose value is being
substituted in the template portion of the query (rvesse: rev 1512504)
* /jena/trunk/jena-arq/src/test/java/com/hp/hpl/jena/sparql/api/TestAPI.java
> SPARQL optimizer does not consider pre-bound variables, creates wrong query
> ---------------------------------------------------------------------------
>
> Key: JENA-500
> URL: https://issues.apache.org/jira/browse/JENA-500
> Project: Apache Jena
> Issue Type: Bug
> Components: Optimizer
> Affects Versions: Jena 2.10.2
> Reporter: Holger Knublauch
> Assignee: Andy Seaborne
> Fix For: Jena 2.10.2
>
> Attachments: TestPreboundFilter.java
>
>
> There is a regression bug somewhere between 2.7.2 and 2.10.2.
> See test case which works green in the old version but fails on the
> latest snapshot. I believe the cause is that
> TransformFilterImplicitJoin.testSpecialCaseUnused() incorrectly assumes
> it can ignore the whole query if it encounters unbound variables.
> However, in my case the variables do have values, coming from the
> initial binding of the QueryExecution.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
