You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Stephen Owens (JIRA)" <ji...@apache.org> on 2017/05/04 13:34:04 UTC
[jira] [Commented] (JENA-1332) Possibly incorrect results from
SPARQL with union and filter not exists
[ https://issues.apache.org/jira/browse/JENA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996729#comment-15996729 ]
Stephen Owens commented on JENA-1332:
-------------------------------------
Thanks Andy, this lead to a robust discussion about SPARQL evaluation order and binding. The end result is, we agree and we learned something. I'll close the issue as invalid.
> Possibly incorrect results from SPARQL with union and filter not exists
> -----------------------------------------------------------------------
>
> Key: JENA-1332
> URL: https://issues.apache.org/jira/browse/JENA-1332
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: Jena 3.2.0
> Reporter: Stephen Owens
> Attachments: JenaFilterNotExistsUnionTest.java
>
>
> The test case attached to this issue shows an unexpected SPARQL result. We found the result while optimizing some SPARQL that had poor performance with some OPTIONAL clauses. We thought the optimization was the same as the original but in version 3.2.0 the result differs, it worked in 3.0.0.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)