Andy Seaborne created JENA-1928:
---
Summary: Logging improvements.
Key: JENA-1928
URL: https://issues.apache.org/jira/browse/JENA-1928
Project: Apache Jena
Issue Type: Improvement
Affects
[
https://issues.apache.org/jira/browse/JENA-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse reassigned JENA-1927:
---
Assignee: Rob Vesse
> First time usage confusing message Unable to check TDB lock owner, the lock
>
[
https://issues.apache.org/jira/browse/JENA-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17145774#comment-17145774
]
Rob Vesse commented on JENA-1927:
-
Note that this is an error message from a low level sub-system. At the
rvesse opened a new pull request #13:
URL: https://github.com/apache/jena-site/pull/13
Adds an entry to the FAQ for the TDB lock file version mismatch
error to make it easier for users to understand what this error means
and how to go about resolving it.
[
https://issues.apache.org/jira/browse/JENA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17145691#comment-17145691
]
Andy Seaborne commented on JENA-1926:
-
The queries do not have the same structure, the position of
[
https://issues.apache.org/jira/browse/JENA-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17145660#comment-17145660
]
Andy Seaborne commented on JENA-1925:
-
Also:
[
https://issues.apache.org/jira/browse/JENA-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17145053#comment-17145053
]
Wolfgang Fahl commented on JENA-1927:
-
Indeed the suggestion works - just add --tdb2 to the command
Wolfgang Fahl created JENA-1927:
---
Summary: First time usage confusing message Unable to check TDB
lock owner, the lock file contents appear to be for a TDB2 database. Please
try loading this location as a TDB2 database.
Key:
Julian Gonggrijp created JENA-1926:
--
Summary: Query execution speed depends more on WHERE clause order
than expected
Key: JENA-1926
URL: https://issues.apache.org/jira/browse/JENA-1926
Project:
[
https://issues.apache.org/jira/browse/JENA-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144916#comment-17144916
]
Elie Roux commented on JENA-1925:
-
Ah, thanks, that probably solves the problem. A complete mvn project
[
https://issues.apache.org/jira/browse/JENA-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Vesse closed JENA-1925.
---
Resolution: Duplicate
This report does not contain sufficient information to diagnose the problem,
when
Elie Roux created JENA-1925:
---
Summary: missing dependency to commons-codec in jena-arq pom
Key: JENA-1925
URL: https://issues.apache.org/jira/browse/JENA-1925
Project: Apache Jena
Issue Type: Bug
[
https://issues.apache.org/jira/browse/JENA-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144732#comment-17144732
]
Jonas Sourlier commented on JENA-1918:
--
Thank you Andy!
> Bad performance of path sequence and path*
[
https://issues.apache.org/jira/browse/JENA-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1898:
Description:
I have a project where the dependency resolution causes the commons-codec from
Apache
[
https://issues.apache.org/jira/browse/JENA-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-1898:
Summary: Force commons-codec dependency to be Jena parent POM choice (was:
Force commons-code
15 matches
Mail list logo