[ 
https://issues.apache.org/jira/browse/JENA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856399#comment-13856399
 ] 

Andy Seaborne edited comment on JENA-432 at 12/24/13 5:41 PM:
--------------------------------------------------------------

Commit 1553306 from [~andy.seaborne] in branch 'jena/trunk'
[ https://svn.apache.org/r1553306 ]

JENA-595 , JENA-432 , JENA-616 , JENA-293 , JENA-383

Put filter equality rewrite after filter placement because
it may then be possible to apply it when it could not when
covering a larger pattern.

Modify some tests that were sensitive to this.


was (Author: jira-bot):
Commit 1553306 from [~andy.seaborne] in branch 'jena/trunk'
[ https://svn.apache.org/r1553306 ]

JENA-595 , JENA-432 , JENA-616 , JENA-293 , JENA-383

Put filter equality rewrite after filter placement because
it may then be possible to apply it when it could not when
covering a larger pattern.

Modify some test that were sensitive to this.

> Filter optimization messes up when a nested select is present in the same 
> block
> -------------------------------------------------------------------------------
>
>                 Key: JENA-432
>                 URL: https://issues.apache.org/jira/browse/JENA-432
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: ARQ, Optimizer
>    Affects Versions: Jena 2.10.0
>            Reporter: Simon Helsen
>            Assignee: Andy Seaborne
>             Fix For: Jena 2.10.1
>
>
> The following test query:
> {noformat}
> SELECT ?test ?s1
> WHERE {
>   ?test ?p1 ?o1.
>   FILTER ( ?test = <http://localhost/t1> || ?test = <http://localhost/t2> )  
>   OPTIONAL {
>     SELECT ?s1
>     { ?s1 ?p2 ?o2 }
>   }
> }
> {noformat}
> produces the following plan:
> {noformat}
> (project (?test ?s1)
>   (disjunction
>     (table empty)
>     (table empty)))
> {noformat}
> Something goes wrong with the FILTER expansion. As a workaround, we observed 
> that the following variation:
> {noformat}
> SELECT ?test ?s1
> WHERE {
>   { ?test ?p1 ?o1.
>     FILTER ( ?test = <http://localhost/t1> || ?test = <http://localhost/t2> ) 
>  
>   }
>   OPTIONAL {
>     SELECT ?s1
>     { ?s1 ?p2 ?o2 }
>   }
> }
> {noformat}
> produces the correct plan:
> {noformat}
> (project (?test ?s1)
>   (leftjoin
>     (disjunction
>       (assign ((?test <http://localhost/t1>))
>         (bgp (triple <http://localhost/t1> ?p1 ?o1)))
>       (assign ((?test <http://localhost/t2>))
>         (bgp (triple <http://localhost/t2> ?p1 ?o1))))
>     (project (?s1)
>       (bgp (triple ?s1 ?/p2 ?/o2)))))
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to