[jira] [Closed] (JENA-2337) Dataset of WHERE clause in UPDATEs only contains the default graph if using-graph-uri is given

["Andy Seaborne (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JENA-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Seaborne closed JENA-2337.
-------------------------------
    Resolution: Not A Problem

> Dataset of WHERE clause in UPDATEs only contains the default graph if using-graph-uri is given
> ----------------------------------------------------------------------------------------------
>
>                 Key: JENA-2337
>                 URL: https://issues.apache.org/jira/browse/JENA-2337
>             Project: Apache Jena
>          Issue Type: Bug
>    Affects Versions: Jena 4.3.2
>            Reporter: Holger Knublauch
>            Priority: Major
>
> Summary: I think this boils down to DynamicDatasetGraph in DynamicDatasets: the provided baseDSG is never used except for cloning the context. The private function getProjected is never used anywhere, see
> https://github.com/apache/jena/blob/main/jena-arq/src/main/java/org/apache/jena/sparql/core/DynamicDatasets.java#L117
> The problem occurs when we call a SPARQL UPDATE with using-graph-uri which we map to UpdateWithUsing.addUsing. On execution of such an update, this triggers a code path that goes through DynamicDatasets.dynamicDataset. The result is that the WHERE clause of an UPDATE only gets to see the default graph, but none of the other named graphs in the original dataset. Then, the GRAPH <...> clause does not work correctly.
> My understanding of the USING/using-graph-uri contract is that this only sets the default graph yet all other graphs in the dataset remain visible. Is this not the case?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: jira-unsubscribe@jena.apache.org
For additional commands, e-mail: jira-help@jena.apache.org