[
https://issues.apache.org/jira/browse/JENA-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086127#comment-15086127
]
Andy Seaborne commented on JENA-1111:
-------------------------------------
It is also worth considering whether this ought to be the local execution
mechanism as well. The semantics are not identical in the presence of nested
selects but it does look like more usual cases are covered.
Maybe then {{QueryExecutionFactory.create(.... QuerySolution)}} can be
deprecated/removed (this will take several release cycles - it is long-time API
operations).
> Use QueryTransformOps/UpdateTransformOps for remote execution
> -------------------------------------------------------------
>
> Key: JENA-1111
> URL: https://issues.apache.org/jira/browse/JENA-1111
> Project: Apache Jena
> Issue Type: Improvement
> Reporter: Andy Seaborne
> Priority: Minor
>
> QueryExecutionFactory uses prebinding to process QuerySolution provided for
> execution. (This is built in to execution: query engines allow an initial
> binding) That does not work for remote execution.
> JENA-976 brought in a syntax-rewrite engine.
> That could be used to provide pre-binding-like functionality for remote
> operations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
