[ https://issues.apache.org/jira/browse/JENA-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501275#comment-17501275 ]
Andy Seaborne commented on JENA-2293: ------------------------------------- Done with: Commit 1e075c9c52b74b0479a474813bed5b274c9ea2e8 in jena's branch refs/heads/main from Andy Seaborne [ https://gitbox.apache.org/repos/asf?p=jena.git;h=1e075c9 ] Commit b8736221e0057439ee7714637b193baaeb518c0e in jena's branch refs/heads/main from Andy Seaborne [ https://gitbox.apache.org/repos/asf?p=jena.git;h=b873622 ] > 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)