On 24/05/17 10:39, Laura Morales wrote:
Oh thank you, this makes sense! I spent hours to understand that part of the
documentation :)
A couple of related questions:
1) Do I have to use text:entityField "uri" or can I replace "uri" with anything? Like "iri",
"foo", "bar", ...
Anything.
2) say I create an <#entMap> for each graph in the dataset, and use text:graphField
"some-graph" in each <#entMap>. Can I define Lucene fields with the same name on
different graphs? Or will fields with the same name be merged all together across all graphs?
I have not used the named graph support so I'm not sure.
Andy
-----------------------------------------------------------------------
Question 1) If I want to add more indexes, do I just add more of "text:entityMap <#entMap>" to <#indexLucene>?
Like "text:entityMap <#entMap-1>", "text:entityMap <#entMap-2>", etc...
They are all held in the same Lucene file (index) but, yes, that indexes
different properties.
Question 2) I don't understand what's going on in <#entMap>. What are
entityField, defaultField, and how does mapping work?!
jena-text uses a different Lucene field (string name) for each property
indexed.
The default is the Lucene default field - a Lucene concept - the lucene
query string can access multiple fields in one query. See the Lucene
documentation for details.
The entity field is the thing being indexed - the result - Lucene is a
inverted index.
Andy
