Re: Jena native store indexes

When writing SPARQL queries, should I be aware of any particular index? Should I create new indexes myself (how)? You 'can' create text-indexes for selected properties of your data for text search with a much better performance:

ArrayIndexOutOfBounds exception on un-synchronized model modifications?

I expect the answer to my question is simply "make sure model access is synchronized", but just in case, I'm wondering whether this is expected behavior. Here's some code that modifies a model from a bunch of different threads. This doesn't cause an error every time, but occasionally throws, as

Re: Jena native store indexes

But is Jena (or any RDF store for what matters) expected to perform well even if I don't explicitly add any index? > You 'can' create text-indexes for selected properties of your data for > text search with a much better performance: > >

Re: ArrayIndexOutOfBounds exception on un-synchronized model modifications?

Yes, you will want to exercise some control over concurrency here: https://jena.apache.org/documentation/notes/concurrency-howto.html --- A. Soroka The University of Virginia Library > On Apr 11, 2017, at 1:16 PM, Joshua TAYLOR wrote: > > I expect the answer to my

Re: Jena native store indexes

The Jena list can't really answer questions about "any RDF store", but for TDB, you begin with basic covering indexes, so you do not need to add anything (in fact you cannot add anything) to provide more indexing for standard SPARQL forms. As has been pointed out, there are _extensions_ to

Jena native store indexes

With RDBMSes, indexes are a bit topic and should always be taken into consideration when writing queries. With RDF stores instead, I barely see them mentioned at all. So I was wondering how indexes work in Jena native store, or other native stores in general. When writing SPARQL queries, should