[
https://issues.apache.org/jira/browse/JENA-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827887#comment-15827887
]
ASF subversion and git services commented on JENA-1280:
-------------------------------------------------------
Commit f07bff3bfe909f9fa032ac4c0ce03414ac9ec5de in jena's branch
refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=f07bff3 ]
JENA-1280: Variables in BGPs in EXISTS should not block join->sequence.
> JoinClassifer is too cautious with EXISTS variables.
> ----------------------------------------------------
>
> Key: JENA-1280
> URL: https://issues.apache.org/jira/browse/JENA-1280
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: Jena 3.1.1
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
>
> This query
> {noformat}
> SELECT * {
> :s :p ?g # ?g
> GRAPH ?g { # ?g
> :s1 :p1 ?x
> FILTER EXISTS { ?s ?p ?o }
> }
> }
> {noformat}
> is not executed as a {{(sequence)}} because there are variables in the
> {{FILTER}} that appear to be not bound: {{?s}} etc in {{EXISTS}}. If it were
> a function, this would be correct but {{EXISTS}} is different.
> Variables only in an {{EXISTS}} BGP patterns should not contribute to the
> unsafe variables of a {{FILTER}}.
> This query:
> {noformat}
> SELECT * {
> ?s :p ?g # :s -> ?s
> GRAPH ?g {
> :s1 :p1 ?x
> FILTER EXISTS { ?s ?p ?o }
> }
> }
> {noformat}
> is not safe to allow {{?s}} to substitute. This is correctly detected in
> Jena 3.1.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
