[
https://issues.apache.org/jira/browse/JENA-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15428259#comment-15428259
]
Andy Seaborne commented on JENA-1225:
-------------------------------------
The problem is with Fuseki - PUT clears out a graph and removes prefixes,
DELETE does not touch the prefixes. But the PUT after DELETE does not see a
graph to be cleared out so the prefix removing code is not called.
We should make the removeGraph contract include removing prefixes so the PR
looks good.
TDB needs the fix as well. TDB uses a different part of the DataetGraph
hierarchy (specifically, {{DatasetGraphTriplesQuads}}) and the notion of
"graph" has gone by then. Action on me.
Incidentally, {{PrefixMapping}} lacks a clear operation; I'll add one. (Delete
on the default graph is a clear, not removal).
> Prefixmappings are not removed permanently from graph with DELETE
> -----------------------------------------------------------------
>
> Key: JENA-1225
> URL: https://issues.apache.org/jira/browse/JENA-1225
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Fuseki 2.4.0
> Environment: Any / appears on Fuseki 2.4.0 or older
> Reporter: Miika Alonen
> Priority: Minor
>
> Prefixmappings are not removed permanently from graphs with DELETE. When
> adding triples to a graph that was deleted earlier old prefixmappings appear
> unexpectedly.
> EXAMPLE:
> PUT http://localhost:3030/example/data?graph=http://example.org/foo#
> @prefix foo: <http://example.org/foo#> .
> foo:foo foo:foo foo:foo
> DELETE http://localhost:3030/example/data?graph=http://example.org/foo#
> PUT http://localhost:3030/example/data?graph=http://example.org/foo#
> @prefix bar: <http://example.org/bar#> .
> bar:bar bar:bar bar:bar .
> GET http://localhost:3030/example/data?graph=http://example.org/foo#
> This returns both old and new prefixmappings:
> @prefix bar: <http://example.org/bar#> .
> @prefix foo: <http://example.org/foo#> .
> bar:bar bar:bar bar:bar .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
