[ https://issues.apache.org/jira/browse/JENA-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498590#comment-17498590 ]
Andy Seaborne commented on JENA-2293: ------------------------------------- The original title: "SPARQL Update: NPE when COPY or MOVE to non-existing graph" changed to "SPARQL Update: DatasetGraphOne: NPE when COPY or MOVE to named graph" To anyone reading this: This is specific to {{DatasetGraphOne}} and its javadoc states that named graph can not be added. "CREATE" will fail with an UnsupportedOperationException on {{DatasetGraphOne}}. A dataset created with {{DatasetFactory.create(graph)} works and does automatically create graphs as needed. > 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)