> On Dec 15, 2018, at 9:59 AM, Marco Neumann wrote:
>
>> *Question*: does that make sense to have a unique Lucene index for text and
>> space ?
>> It is possible at all? If yes, is it good in terms of disk space and
>> performance?
>> Like this:
>> <#indexLucene> a text:TextIndexLucene ;
>>
What is the advantage to doing that as opposed to using Jena's built-in
in-memory dataset?
ajs6f
> On Dec 15, 2018, at 3:04 AM, Siddhesh Rane wrote:
>
> Bring the entire database in RAM.
> Use "vmtouch "
> Get vmtouch from https://hoytech.com/vmtouch/
>
> I had used jena for 150M triples and
yes that is correct Jean-Marc two indexes, one for spatial and another for
text data.
please be advised that the Jena project will introduce a new spatial
indexer in an upcoming release that you might want to consider for your
evaluation since you only start out with spatial queries at this
I began to try using what I sketched in the preceding post:
https://github.com/jmvanel/semantic_forms/blob/master/scala/forms/src/main/scala/deductions/runtime/jena/lucene/LuceneIndex.scala#L88
But it does not work: that is, a spatial query returns nothing.
To create the spatial index by program
Bring the entire database in RAM.
Use "vmtouch "
Get vmtouch from https://hoytech.com/vmtouch/
I had used jena for 150M triples and my performance findings are documented
at
https://lists.apache.org/thread.html/254968eee3cd04370eafa2f9cc586e238f8a7034cf9ab4cbde3dc8e9@%3Cusers.jena.apache.org%3E
