[jira] [Commented] (JENA-1000) tdbdump / tdbloader sequence corrupts rdf:type predicates
[
https://issues.apache.org/jira/browse/JENA-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14680111#comment-14680111
]
Donald Pellegrino commented on JENA-1000:
-
The broken run of tdbloader makes sense. If I find input for reliable
reproduction I will post that in the future. Note that the TDB database
exhibiting the corruption had been loaded with multiple tdbloader sessions as
well as uploads of files to the Apache Jena Fuseki interface over time. Some of
those operations may have been terminated before completion. Enhancements to
the bulk loaders that prevent database corruption may get at the root cause of
this issue.
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)
[jira] [Commented] (JENA-1000) tdbdump / tdbloader sequence corrupts rdf:type predicates
[
https://issues.apache.org/jira/browse/JENA-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (JENA-1000) tdbdump / tdbloader sequence corrupts rdf:type predicates
[
https://issues.apache.org/jira/browse/JENA-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14646224#comment-14646224
]
Andy Seaborne commented on JENA-1000:
-
See thread on users@jena about using tdbloader. This observation would be
explained by a partial, aborted TDB load operation.
What is {{custom:}}?
{{custom:200501898-4-1}] must appear in the data if that update has any effect.
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
Priority: Critical
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)
[jira] [Commented] (JENA-1000) tdbdump / tdbloader sequence corrupts rdf:type predicates
[
https://issues.apache.org/jira/browse/JENA-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640961#comment-14640961
]
Andy Seaborne commented on JENA-1000:
-
Please could you provide a short data file that shows the problem for you.
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
Priority: Critical
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)
