Since I don't think anyone answered your specific original question
TDB and TDB2 both use dictionary encoding (and in fact most RDF stores use some
variation on this). Basically they map each unique RDF term (whether URI,
string, blank node etc) to a consistent internal identifier and use this
Hello, Sorin, thank you for this contribution!
Osma and Chris, you guys know the most about the text index by far-- would this
make sense as part of the documentation for that module?
ajs6f
> On Feb 5, 2019, at 7:07 AM, Sorin Gheorghiu
> wrote:
>
> Hi,
>
> it is a great that Jena supports f
Are you asking how to use an extant Lucene index with your text documents in it
for Jena's text index as well?
ajs6f
> On Feb 14, 2019, at 6:23 AM, Mikael Pesonen
> wrote:
>
>
> Hi,
>
> Our system stores documents with separate rest API and document id's are
> stored, along with document m
If you are using the same identifiers in each source, then when you merge them
the common identifiers will immediately form links.
ajs6f
> On Feb 18, 2019, at 7:24 AM, elio hbeich wrote:
>
> Can you explain more this part:
> '' If you want to link the two, simply add both to a model or tdb dat
Hey Andy,
Sorry I don’t mean to be agonisingly thick but I’m not sure I follow the
conclusion and I don’t get how to modify the config file that I had attached
for a TDB config.
I didn’t modify the data on disc model. I added a sparql update method to the
inference model and I removed the expl
Meanwhile I found the root cause in the config file, the path for the
Lucene directory was wrong.
<#indexLucene> a text:TextIndexLucene ;
text:directory ;
...
Regards
Weitergeleitete Nachricht
Betreff:Running Fuseki 3.10 with Apache Tomcat
Datum: Mon, 18 Feb
Hi Sorin,
What's the config file?
And there should be some other info in catalina.out or other log file.
openIndexWriter is part of Lucene and at Jena 3.10.0, the lucene version
upgraded from 6.x to 7.4.x.
You can try extrscting the dastaset configuration from config.ttl and
run from the co
