Re: Setting error handler for WriterGraph/DatasetRIOT

On 26/07/16 16:14, Martynas Jusevičius wrote: But the assumption obviously doesn't hold? Illegal Models exist because they can be parsed. No - because someone turned the checking off or created them them with code, not a parser. Wouldn't it make sense for the Writers check URIs just like

Re: Setting error handler for WriterGraph/DatasetRIOT

Which serialization format are you working with? Andy On 25/07/16 22:44, Martynas Jusevičius wrote: Hey, I was planning to set an ErrorHandler on WriterGraphRIOT instance, but it turns such setter does not exist. My ErrorHandler allows invalid URIs to be read without throwing exceptions.

Jena TDB OOME GC overhead limit exceeded

Hi. I've got a repeatable problem with Jena 3.1 when performing a bulk load. The bulk load converts a file into ~200k quads and adds them to a TDB instance within a normal begin write, add quads and commit. Initially this completes in 30-40 seconds, However if I repeat the process (with the same

Re: Setting error handler for WriterGraph/DatasetRIOT

Is there a particular reason you want/need to move malformed data around? It seems like this is just a problem waiting to happen On 26/07/2016 09:34, "Martynas Jusevičius" wrote: RDF/XML (plain) in this case. I would of course prefer a format-agnostic solution.

Re: Setting error handler for WriterGraph/DatasetRIOT

RDF/XML (plain) in this case. I would of course prefer a format-agnostic solution. On Tue, Jul 26, 2016 at 10:21 AM, Andy Seaborne wrote: > Which serialization format are you working with? > > Andy > > > On 25/07/16 22:44, Martynas Jusevičius wrote: >> >> Hey, >> >> I was

Re: Setting error handler for WriterGraph/DatasetRIOT

Turtle-class syntaxes print bad URIs. For RDF/XML, does setting "allowBadURIs" work? https://jena.apache.org/documentation/io/rdfxml_howto.html#advanced-rdfxml-output Andy On 26/07/16 09:34, Martynas Jusevičius wrote: RDF/XML (plain) in this case. I would of course prefer a

Re: Setting error handler for WriterGraph/DatasetRIOT

On 26/07/16 10:23, Martynas Jusevičius wrote: Andy, "allowBadURIs" was my next move, I will try that later today and report back. Any reason why this cannot be exposed uniformly on the WriterRIOT level? Like it is on ReaderRIOT. RDF/XML is the only case that checks IIRC. Writers output what

Jena Rules not working

I have class *Expert*, *Research* and *Student*. Student has Master and Phd subclasses. Expert hasResearch Research, like BernersLee hasResearch Ontologies. Phd Student also have Research like: Khan hasResearch Ontologies. I added a class *StudentExpert* which have no instance but can be created

Re: Setting error handler for WriterGraph/DatasetRIOT

Andy, "allowBadURIs" was my next move, I will try that later today and report back. Any reason why this cannot be exposed uniformly on the WriterRIOT level? Like it is on ReaderRIOT. On Tue, Jul 26, 2016 at 11:15 AM, Andy Seaborne wrote: > Turtle-class syntaxes print bad URIs.

Re: Setting error handler for WriterGraph/DatasetRIOT

What do you mean with "keep the original user input"? We do not want to keep it (as in, process further or store persistently) if it contains invalid URIs. Also, the application is stateless, we do not keep anything in the session (because there is no session). On Tue, Jul 26, 2016 at 11:32 AM,

Re: Web UI of Fuseki doesn't start

Dear Stian, thank you, it helped. Best Regards, Sandor Am 25.07.2016 um 10:47 schrieb Stian Soiland-Reyes: I could replicate this. stain@biggiebuntu:~/Downloads$ java -jar /var/www/fuseki/fuseki-server.jar --update --mem /ds 09:45:20 INFO Dataset: in-memory 09:45:20 WARN No such

Re: Setting error handler for WriterGraph/DatasetRIOT

Rob, the purpose is round-tripping user input. If the user provided invalid URI values, they need to be presented back to the user with an error message, giving him/her a chance to correct the errors. This requires being able to both read and write Models with invalid URIs. We make sure however,

Re: Jena generic rules

Hello Chao, the query should work, yes. Kind regards, Lorenz > would this query work? > SELECT ?x WHERE (?x rdf:type ont:Student . ?x rdf:type ont:Teacher) > > From: javed khan [javedbtk...@gmail.com] > Sent: Monday, July 25, 2016 2:33 PM > To:

Re: Setting error handler for WriterGraph/DatasetRIOT

OK. But how do you handle invalid URI input without turning the checking off? And without reading and then writing the Model? Where the user provides URIs manually, e.g. as a form input for SPARQL endpoint URI. On Tue, 26 Jul 2016 at 20:27, Andy Seaborne wrote: > On 26/07/16

Re: Setting error handler for WriterGraph/DatasetRIOT

On 3.0.1 RDFWriter w = model.getWriter("RDF/XML"); w.setProperty("allowBadURIs", true); does not work -- calls RDFWriterRIOT.setProperty() instead of BaseXMLWriter.setProperty(), so "allowBadURIs" has no effect. Any workaround ideas? On Tue, Jul 26, 2016 at 11:23 AM, Martynas Jusevičius

Re: Jena TDB OOME GC overhead limit exceeded

Dick, The report is embedded in your application setup with a lot of "org.iungo.dataset.bulkload" Just because the OOME occurs in TDB does not mean that the space is consumed in TDB - there may be a bigger memory hog elsewhere. Could you produce an RDF example? Maybe that file, already

Re: Jena Rules not working

Thanks a lot, error is no longer there but not displaying the required result either i-e instance of StudentExpert class. I, for test case, created instance of StudentExpert and it display it (so no problem in ontology) but when I remove the instance, again it display nothing. It means reasoner

Re: Jena TDB OOME GC overhead limit exceeded

On 26/07/16 10:51, Dick Murray wrote: Hi. Where do you set "transactionJournalWriteBlockMode" please? We don't - its off by default. It's a symbol you can set in the global context. TDB.transactionJournalWriteBlockMode It is the only place that triggers DirectByteBuffers in TDB which I

Re: TDB triple storage

Changed code to use RDFFormat.TURTLE_BLOCKS, Set -Xmx8192m on 16g i7 laptop Still getting out of memory error after running for a while, Any suggestions? On 7/25/16, 4:41 PM, "Andy Seaborne" wrote: >On 25/07/16 21:14, Chao Wang wrote: >> Hi Dave, >> As you suggested, I have

Re: Jena TDB OOME GC overhead limit exceeded

Hi. Where do you set "transactionJournalWriteBlockMode" please? Would you expect to see a large number of [B heap entries in a 3.1 TDB? Dick. On 26 July 2016 at 10:39, Andy Seaborne wrote: > Dick, > > The report is embedded in your application setup with a lot of >

Re: Jena Rules not working

As Dave said, wrong PREFIX declaration. >> >> "Select *" + "where { ?x rdf:type std:StudentExpert }"; >> Moreover, your String concatenation will lead to Select *where { ?x rdf:type std:StudentExpert } i.e. there is a missing whitespace before "where". -- Lorenz Bühmann AKSW

Re: TDB triple storage

On 26/07/16 12:08, Chao Wang wrote: Changed code to use RDFFormat.TURTLE_BLOCKS, Set -Xmx8192m on 16g i7 laptop Still getting out of memory error after running for a while, Any suggestions? A complete, minimal example. That is, something someone else can run, and just large enough to

Re: Jena Rules not working

On 26/07/16 09:53, javed khan wrote: I have class *Expert*, *Research* and *Student*. Student has Master and Phd subclasses. Expert hasResearch Research, like BernersLee hasResearch Ontologies. Phd Student also have Research like: Khan hasResearch Ontologies. I added a class *StudentExpert*

Re: Jena TDB OOME GC overhead limit exceeded

To build clean locally do the following: at the top level: not jena-tdb mvn clean install -Pbootstrap mvn install -Pdev (or "mvn clean install" but that builds and tests a lot more) Andy On 26/07/16 14:25, Andy Seaborne wrote: On 26/07/16 14:11, Dick Murray wrote: Hi. I'll set

Re: TDB triple storage

You are right about the reasoner. I used GenericRuleReasoner and loaded a few rules from external file. This statement reasoner.setOWLTranslation(true) is the cause of the issue. Not sure what it does. On 7/26/16, 7:42 AM, "Andy Seaborne" wrote: >On 26/07/16 12:08, Chao

Re: Jena TDB OOME GC overhead limit exceeded

On 26/07/16 14:11, Dick Murray wrote: Hi. I'll set that and run the process again. As an aside I just pulled Master and TDB won't compile because it's can't find MultiSet? Are there notes on getting the Jena GIT into Eclipse? I want to put a count on the BufferAllocatorMem to see what it's

Re: TDB triple storage

On 26/07/16 15:10, Chao Wang wrote: You are right about the reasoner. I used GenericRuleReasoner and loaded a few rules from external file. This statement reasoner.setOWLTranslation(true) is the cause of the issue. Not sure what it does. It's a horrible horrible hack that finds all explicit

Re: Setting error handler for WriterGraph/DatasetRIOT

But the assumption obviously doesn't hold? Illegal Models exist because they can be parsed. Wouldn't it make sense for the Writers check URIs just like the Readers do? URI validity does not depend on syntax, does it? On Tue, Jul 26, 2016 at 11:32 AM, Andy Seaborne wrote: > On

Re: Jena TDB OOME GC overhead limit exceeded

On 26/07/16 16:51, Dick Murray wrote: Ok, I set that option and I get different OOME from the direct buffer memory. You now have: > java.lang.OutOfMemoryError: > Direct buffer memory So that means the direct memory space has run out, not the heap. You can increase direct memory but that

Re: Jena TDB OOME GC overhead limit exceeded

Ok, I set that option and I get different OOME from the direct buffer memory. I then changed the GC using -XX:+UseG1GC (which still throws the OOME) and I don't get why it's throwing the OOME.!? [Eden: 2372.0M(2372.0M)->0.0B(1036.0M) Survivors: 84.0M->196.0M Heap: