[ https://issues.apache.org/jira/browse/JENA-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680116#comment-14680116 ]
Donald Pellegrino commented on JENA-1000: ----------------------------------------- The "custom:" prefix was not input during any load or insert operations. The 200501898-4-1 predicate appeared to have changed namespaces on its own. > tdbdump / tdbloader sequence corrupts rdf:type predicates > --------------------------------------------------------- > > Key: JENA-1000 > URL: https://issues.apache.org/jira/browse/JENA-1000 > Project: Apache Jena > Issue Type: Bug > Components: TDB > Affects Versions: Jena 2.12.1, Jena 2.13.0 > Environment: Tested with tdbloader and tdbloader2 versions 2.12.1 and > 2.13.0 on Windows/Sun Java 1.7.0_60 and CentOS 6.3/OpenJDK 1.8.0_25. tdbdump > was 2.12.1 on CentOS 6.3/OpenJDK 1.8.0_25. > Reporter: Donald Pellegrino > Assignee: Andy Seaborne > Priority: Critical > Fix For: Jena 3.0.1 > > > Steps to reproduce: > 1. A TDB database was exported to N-Quads with tdbdump. > 2. The dump file was then imported into a new TDB database with tdbloader2. > 3. Observe that all rdf:type predicates were replaced with the same randomly > selected predicate. > Work-around: > A work-around was to run a DELETE/INSERT SPARQL command to reassign rdf:type > predicates after the load: > DELETE { ?s custom:200501898-4-1 ?o } > INSERT { ?s rdf:type ?o } > WHERE { > ?s custom:200501898-4-1 ?o > } > Testing: > The behavior was consistent across multiple reloads of the same dump file. > tdbloader and tdbloader2 were both used for loads and they were run on both > Windows and Linux with the same results. > Note that this is a Critical issue as it leads to silent corruption of user > data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)