[
https://issues.apache.org/jira/browse/JENA-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081244#comment-14081244
]
ASF subversion and git services commented on JENA-754:
------------------------------------------------------
Commit 1614951 from [~andy.seaborne] in branch 'jena/trunk'
[ https://svn.apache.org/r1614951 ]
JENA-754 : Rewrite element for WHERE when an update using WITH.
> Avoid using a wrapper dataset for SPARQL Update WITH
> ----------------------------------------------------
>
> Key: JENA-754
> URL: https://issues.apache.org/jira/browse/JENA-754
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: Jena 2.11.2
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Minor
>
> When processing a SPARQL Update operation that uses WITH, the processing
> engine crates a wrapper dataset {{DatasetGraphAltDefaultGraph}} that catches
> access to the default graph and directs it to the alternative graph.
> This can block optimization of the graph pattern because
> DatasetGraphAltDefaultGraph masks the true storage layer and will use the
> default query pattern executor ({{OpExecutor}} and {{StageGeneratorGeneric}}).
> This is not too serious now that the generic process does some optimization
> but it can be improved by modifying the WHERE clause to wrap it in a GRAPH
> <URI> {...} using {{ElementGraph}} and not using a wrapper dataset. The
> pattern matching proceeds to the underlying storage engine as normal.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
