[jira] [Commented] (JENA-991) OpAsQuery : Combine adjacent ElementPathBlocks

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on JENA-991:
------------------------------------------------------

Commit 84ad58d4a6900a3df8f456ab9cd9e5707a0369b5 in jena's branch refs/heads/master from [~andy.seaborne]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=84ad58d ]

JENA-991: Combine adjacent ElementPathBlocks

Switch tests to stronger conditions for patterns now
made same as original syntax.

> OpAsQuery : Combine adjacent ElementPathBlocks
> ----------------------------------------------
>
>                 Key: JENA-991
>                 URL: https://issues.apache.org/jira/browse/JENA-991
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: ARQ
>    Affects Versions: Jena 3.0.0
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>            Priority: Minor
>             Fix For: Jena 3.0.0
>
>
> Following on from JENA-963.
> A single path block from parsed syntax becomes one ElementPathBlock in the AST, then an OpSequence of OpBGP and OpPath items in the algebra. 
> OpAsQuery does not quite reverse this exactly.  It produces a group 
> Example:
> {code}
> { ?p :property ?o . ?p :p* ?z }
> {code}
> where { ?p :property ?o . ?p :p* ?z } is a single ElementPathBlock producing algebra:
> {code}
> (sequence
>   (bgp (?p :property ?o))
>   (path ?p (path* :p) ?z))
>   )
> {code}
> OpAsQuery currently produces 2 ElementPathBlocks, one for the BGP, one for the path. This different syntax generates equivalent algebra.
> OpAsQuery should attempt to combine adjacent ElementPathBlocks as the ElementGroup is created.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)