[
https://issues.apache.org/jira/browse/JENA-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885616#comment-13885616
]
ASF subversion and git services commented on JENA-494:
------------------------------------------------------
Commit 1562536 from [~rvesse] in branch 'jena/trunk'
[ https://svn.apache.org/r1562536 ]
Some basic analysis of what needs to be done to fix JENA-494 added as comments
> Variables in SERVICE can be written by scoping transforms and not recovered.
> ----------------------------------------------------------------------------
>
> Key: JENA-494
> URL: https://issues.apache.org/jira/browse/JENA-494
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: Jena 2.10.1
> Reporter: Andy Seaborne
>
> {noformat}
> SELECT ?z
> {
> SELECT ?z {
> SERVICE <http://foo> { ?c ?p ?z }
> ?c ?q ?z
> }
> }
> {noformat}
> ==>
> {noformat}
> (project (?z)
> (project (?z)
> (sequence
> (service <http://foo>
> (bgp (triple ?/c ?/p ?z)))
> (bgp (triple ?/c ?/q ?z)))))
> {noformat}
> but the remote request is
> {noformat}
> SELECT * { ?c ?p ?o }
> {noformat}
> so the {{?/c}} and {{?c}} do not join. Note that {{?z}} is not renamed
> because it emerges from the inner projection.
> From:
> http://mail-archives.apache.org/mod_mbox/jena-users/201307.mbox/%3C20130717190649.GA25207%40netestate.de%3E
> Renaming is done by TransformScopeRename, looking for projections which are
> not the top level as it walk back up the tree. The renaming is done by
> Rename.renameVars.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
