I fixed a stupid error in text index URI, resulting from pasting, in new
file jena.spatial+text.assembler.ttl:
https://github.com/jmvanel/semantic_forms/blob/master/scala/jena.spatial%2Btext.assembler.ttl
Now, it reads:
:spatial_dataset rdf:type spatial:SpatialDataset ;
rdf:type text:TextDataset ;
spatial:dataset <#dataset> ;
spatial:index <#indexLucene> ;
text:dataset <#dataset> ;
text:index * <#indexLuceneText>* ;
.
But still it says "Failed to find the text index" .
Le dim. 16 déc. 2018 à 09:34, Jean-Marc Vanel <[email protected]> a
écrit :
> So I tried a new file jena.spatial+text.assembler.ttl with separate
> Lucene indices for spatial and text:
>
> https://github.com/jmvanel/semantic_forms/blob/master/scala/jena.spatial%2Btext.assembler.ttl
>
> It defines a Dataset with both Dataset types and both Lucene indices:
>
> :spatial_dataset rdf:type spatial:SpatialDataset ;
> rdf:type text:TextDataset ;
> spatial:dataset <#dataset> ;
> spatial:index <#indexLucene> ;
> text:dataset <#dataset> ;
> text:index <#indexLucene> ;
> .
>
> Alas , when querying , it says "Failed to find the text index" :
>
> WARN org.apache.jena.query.text.TextQueryPF - Failed to find the text
> index : tried context and as a text-enabled dataset
> WARN org.apache.jena.query.text.TextQueryPF - No text index - no text
> search performed
>
> Is it because rdf:type spatial:SpatialDataset is asserted first in
> assembler file?
> So, defining a hybrid Dataset does not work anymore by TTL specification
> than by JVM code specification.
> I definitely need more experts' advice .
>
>
>
> Le sam. 15 déc. 2018 à 21:10, ajs6f <[email protected]> a écrit :
>
>> > On Dec 15, 2018, at 9:59 AM, Marco Neumann <[email protected]>
>> 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 ;
>> >> a spatial:SpatialIndexLucene ;
>> >> # etc ...
>>
>> I'm sure that would be ideal for many cases, but I'm not at all sure that
>> the same index can answer queries of both kinds. Perhaps we can combine
>> fields from both, but are the relationships between tuple and index record
>> the same in both cases?
>>
>> Otherwise, I know we had a conversation at some point in the past on one
>> of the lists about trying to factor out commonalities between jena-spatial
>> and jena-text, but it didn't go very far at that time and I don't know what
>> the intervening years have done to make it more or less feasible. There
>> have been many changes to jena-text in that time and the new spatial module
>> is a whole new story. I'd put a link here but searching lists.apache.org
>> hasn't brought it up for me.
>>
>> ajs6f
>>
>>
>
> --
> Jean-Marc Vanel
>
> http://www.semantic-forms.cc:9111/display?displayuri=http://jmvanel.free.fr/jmv.rdf%23me#subject
> <http://www.semantic-forms.cc:9111/display?displayuri=http://jmvanel.free.fr/jmv.rdf%23me>
> Rule-based programming, Semantic Web
> +33 (0)6 89 16 29 52
> Twitter: @jmvanel , @jmvanel_fr ; chat: irc://irc.freenode.net#eulergui
> Chroniques jardin
> <http://semantic-forms.cc:1952/backlinks?q=http%3A%2F%2Fdbpedia.org%2Fresource%2FChronicle>
>
--
Jean-Marc Vanel
http://www.semantic-forms.cc:9111/display?displayuri=http://jmvanel.free.fr/jmv.rdf%23me#subject
<http://www.semantic-forms.cc:9111/display?displayuri=http://jmvanel.free.fr/jmv.rdf%23me>
Rule-based programming, Semantic Web
+33 (0)6 89 16 29 52
Twitter: @jmvanel , @jmvanel_fr ; chat: irc://irc.freenode.net#eulergui
Chroniques jardin
<http://semantic-forms.cc:1952/backlinks?q=http%3A%2F%2Fdbpedia.org%2Fresource%2FChronicle>
