Re: Update Query Parsing error

In case of Maven Shade plugin was used for (re-)packaging resp. creating an uber-Jar, add this transformer       On 23.05.2018 17:36, Andy Seaborne wrote: > > > On 23/05/18 16:19, Bart van Leeuwen wrote: >> code: >> >> with apache-jena-libs in pom > > Finding only one init is a symptom

Re: Nodes without dereferenceable URIs

I agree using HTTP URIs is not good practice in any environment where people might expect to dereference them. For a purely local system, though, you would be the only one inconvenienced, and you could always add a web server to provide that service later, if you felt the need for it. Otherwise,

Re: Nodes without dereferenceable URIs

> Maybe you can tell us more about your use case(s) and the workflow(s) with > which you expect to use this data? A graph of my own documents, books, papers, that I have on my computer.     Sent: Wednesday, May 23, 2018 at 4:34 PM From: ajs6f To: users@jena.apache.org

Re: Update Query Parsing error

On 23/05/18 16:19, Bart van Leeuwen wrote: code: with apache-jena-libs in pom Finding only one init is a symptom repacked jars that have not the right ServiceLoader files. It looks like classpath has a repacked set of jena jars on it or a jar with jena inside it, as well as those from

Re: Update Query Parsing error

code: with apache-jena-libs in pom ## public static void main(String... args) { JenaSystem.DEBUG_INIT = true; String update = "INSERT DATA {}"; UpdateFactory.create(update); System.out.println("DONE"); } ### This is what I get

Re: Update Query Parsing error

I ran with 3.7.0 (and 3.6.0 and 3.5.0) public static void main(String... args) { JenaSystem.DEBUG_INIT = true; String update = "INSERT DATA {}"; UpdateFactory.create(update); System.out.println("DONE"); } and public static void main(String...

Re: Update Query Parsing error

On 23/05/18 12:40, Bart van Leeuwen wrote: I mean this: # public static void main(String[] args) throws Exception {       JenaSystem.DEBUG_INIT = true;         JenaSystem.init();         ARQ.getContext().isTrue(ARQ.constantBNodeLabels) ; which crashes at the ARQ line. And no

Re: Update Query Parsing error

and with 3.7 ? Met Vriendelijke Groet / With Kind Regards Bart van Leeuwen twitter: @semanticfire tel. +31(0)6-53182997 Netage B.V. http://netage.nl Esdoornstraat 3 3461ER Linschoten The Netherlands From: ajs6f To: users@jena.apache.org Date: 23-05-2018 16:24

Re: Nodes without dereferenceable URIs

Maybe you can tell us more about your use case(s) and the workflow(s) with which you expect to use this data? There is no general best practice here, but there are techniques that are better and worse for some given situation. ajs6f > On May 23, 2018, at 10:31 AM, Laura Morales

Re: Nodes without dereferenceable URIs

I could do that, but can it be considered good practice? Other approaches are - make my own URI scheme, for example - make my own URN NID like but NIDs are supposed to be registered - the info: scheme has been deprecated, so I should not use I don't think RDF is providing any "best

Re: Update Query Parsing error

Runs fine for me against current master. ajs6f > On May 23, 2018, at 7:40 AM, Bart van Leeuwen > wrote: > > I mean this: > > # > > public static void main(String[] args) throws Exception { > JenaSystem.DEBUG_INIT = true; >

Re: Nodes without dereferenceable URIs

Can you use HTTP URIs that simply don't point to an actual server? (E.g. http://lauras.namespace/blah/blah/blah) If no one tries to dereference them, it's fine if they don't work. If someone might try to dereference them, that's when you might have problems. ajs6f > On May 22, 2018, at 2:01

Re: Update Query Parsing error

I mean this: # public static void main(String[] args) throws Exception { JenaSystem.DEBUG_INIT = true; JenaSystem.init(); ARQ.getContext().isTrue(ARQ.constantBNodeLabels) ; which crashes at the ARQ line. Met Vriendelijke Groet / With Kind Regards Bart

Re: Update Query Parsing error

On 23/05/18 12:15, Bart van Leeuwen wrote: I just tried your little addition and indeed it crashes before the update. So what's next ? To be clear here - you mean this: public static void main(String[] args) throws Exception { JenaSystem.DEBUG_INIT = true;

Re: Comparison method violates its general contract!

Here is the log, I'll try to come up with short example and data [2018-05-23 14:16:38] Fuseki WARN  [1771] RC = 500 : Comparison method violates its general contract! java.lang.IllegalArgumentException: Comparison method violates its general contract!     at

Re: Update Query Parsing error

I just tried your little addition and indeed it crashes before the update. So what's next ? Met Vriendelijke Groet / With Kind Regards Bart van Leeuwen twitter: @semanticfire tel. +31(0)6-53182997 Netage B.V. http://netage.nl Esdoornstraat 3 3461ER Linschoten The Netherlands From: Andy

Re: Comparison method violates its general contract!

The issue is data and query dependent. A shorter query and some data please! Andy On 23/05/18 12:05, Mikael Pesonen wrote: How do I get it? The log file. Fuseki is not crashing, just returns then error. Br On 23.5.2018 13:40, Rob Vesse wrote: A stack trace would be helpful...

Re: Update Query Parsing error

This code has the same Jena sequence without the StarDog code: The stacktrace indicates an exception before parsing even starts so the update itself is not a factro. public static void main(String... args) { JenaSystem.DEBUG_INIT = true; String update = "INSERT DATA {}";

Re: Comparison method violates its general contract!

How do I get it? Fuseki is not crashing, just returns then error. Br On 23.5.2018 13:40, Rob Vesse wrote: A stack trace would be helpful... Rob On 23/05/2018, 11:15, "Mikael Pesonen" wrote: Hi, I'm geting this Java error with following query

Re: Comparison method violates its general contract!

A stack trace would be helpful... Rob On 23/05/2018, 11:15, "Mikael Pesonen" wrote: Hi, I'm geting this Java error with following query (prefixes omitted) with Jena Fuseki 3.6.0 . Query works if every ?property_type is collected instead of

Comparison method violates its general contract!

Hi, I'm geting this Java error with following query (prefixes omitted) with Jena Fuseki 3.6.0 . Query works if every ?property_type is collected instead of sampling. It also works if ?label is not collected (?property_type is sampled). SELECT DISTINCT ?p ?label ?range