You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (Jira)" <ji...@apache.org> on 2022/02/27 13:23:00 UTC
[jira] [Updated] (JENA-2293) SPARQL Update: DatasetGraphOne: NPE when COPY or MOVE to named graph
[ https://issues.apache.org/jira/browse/JENA-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Seaborne updated JENA-2293:
--------------------------------
Summary: SPARQL Update: DatasetGraphOne: NPE when COPY or MOVE to named graph (was: SPARQL Update: NPE when COPY or MOVE to non-existing graph)
> SPARQL Update: DatasetGraphOne: NPE when COPY or MOVE to named graph
> --------------------------------------------------------------------
>
> Key: JENA-2293
> URL: https://issues.apache.org/jira/browse/JENA-2293
> Project: Apache Jena
> Issue Type: Bug
> Affects Versions: Jena 4.4.0
> Reporter: Richard Cyganiak
> Assignee: Andy Seaborne
> Priority: Major
> Attachments: SPARQLUpdateTest.java
>
>
> When executing SPARQL Update requests against a dataset that does not automatically create new graphs, COPY or MOVE operations with a non-existing graph as the target will result in a NullPointerException. The same happens when adding SILENT.
> I would expect these requests to result in UpdateExceptions, with a message pointing out the non-existing graph. Or nothing in the case of SILENT.
> The attached JUnit 4 test demonstrates this by running queries against a DatasetGraphOne:
> COPY DEFAULT TO <http://example.org/no-such-graph>
> COPY SILENT DEFAULT TO <http://example.org/no-such-graph>
> MOVE DEFAULT TO <http://example.org/no-such-graph>
> MOVE SILENT DEFAULT TO <http://example.org/no-such-graph>
> Each request produces an NPE.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)