Error during text index

Hello, Jena text index returned the following error: # java -cp /opt/apache-jena-fuseki-2.3.1/fuseki-server.jar jena.textindexer --desc=/etc/default/fuseki/jena-text-config.ttl java.lang.UnsupportedOperationException: http://d-nb.info/standards/elementset/gnd#SeriesOfConferenceOrEvent is not

Re: Error during text index

Hi Sorin, I'm curious as to why you are indexing a URI and what you see the benefit of that. You might at least want to set the analyser carefully. Andy PS I fixed the cause of the "UnsupportedOperationException" but only in the sense that it now issues a warning and skips the non-l

Re: Error during text index

Hi Andy, I need just the type of the entry, from the example just the last part 'SeriesOfConferenceOrEvent'. If possible I would set an analyser which would trim the first part, but I don't know how. Thanks Sorin Am 28.04.2016 um 17:25 schrieb Andy Seaborne: Hi Sorin, I'm curious as to w

Re: Error during text index

Hi Sorin! Why do you need the type in the text index? The text index is designed to store literals. It does not know how to handle URIs at all. Generally what you would do to combine text search with a restriction on rdf:type is to use separate query patterns, e.g. { ?s text:query 'nucle

Re: Error during text index

Hi Osma, I do need the type in the text index to get faster results than using sparql queries. I found an analyzer which could replace the URI with the string type, but I cannot use it as long as the non-literal are skiped. http://d-nb.info/standards/elementset/

Re: Error during text index

The use of rdf:type seems to mix being a displayable label and a class type. Maybe adding skos:prefLabel to keep the display label is worth doing. You can extract the fragment from a URI with: STRAFTER(STR(), "#")' (untested): INSERT { ?s skos:prefLabel ?label } WH

Re: Error during text index

Hi Andy, thank you for your suggestion, I will use this workaround. Regards, Sorin Am 29.04.2016 um 12:20 schrieb Andy Seaborne: The use of rdf:type seems to mix being a displayable label and a class type. Maybe adding skos:prefLabel to keep the display label is worth doing. You can extrac

Re: Error during text index

Hi Andy, after 2 attempts to insert the new SKOS variable, I got the following error: org.apache.jena.query.text.TextIndexException: org.apache.solr.client.solrj.SolrServerException: IOException occured when talking to server at: http://localhost:8983/solr/GND100316_550 ..

Fwd: Re: Error during text index

-- Betreff: Re: Error during text index Datum: Mon, 2 May 2016 20:05:37 +0200 Von:Sorin Gheorghiu An: users@jena.apache.org Hi Andy, after 2 attempts to insert the new SKOS variable, I got the following error: org.apache.jena.query.text.TextInde

Re: Fwd: Re: Error during text index

estart, it looks like the indexes aren't corrupted. Thus, it seems the error isn't critical and I may ignore it. But my expectation was that the insert command will add the new parameter to Jena TDB and not to Solr. Weitergeleitete Nachricht ---- Betreff: Re: Error dur

Re: Fwd: Re: Error during text index

Sorin Gheorghiu wrote: After Solr server restart, it looks like the indexes aren't corrupted. Thus, it seems the error isn't critical and I may ignore it. But my expectation was that the insert command will add the new parameter to Jena TDB and not to Solr. Weitergeleitete Nachrich

Re: Fwd: Re: Error during text index

:50, Sorin Gheorghiu wrote: After Solr server restart, it looks like the indexes aren't corrupted. Thus, it seems the error isn't critical and I may ignore it. But my expectation was that the insert command will add the new parameter to Jena TDB and not to Solr. Weitergeleite

Re: Fwd: Re: Error during text index

ignore it. But my expectation was that the insert command will add the new parameter to Jena TDB and not to Solr. Weitergeleitete Nachricht Betreff: Re: Error during text index Datum: Mon, 2 May 2016 20:05:37 +0200 Von: Sorin Gheorghiu An:

Re: Fwd: Re: Error during text index

On 13/05/16 09:45, Sorin Gheorghiu wrote: Hi Andy, I found on the server a coredump reporting insufficient memory for the JRE (see attach). It is weird, fuseki allocates a 32Gb maximum Java heap size, but it uses only 16Gb: # java -Xmx32G -jar fuseki-server.jar --update --config=/etc/default/