Correction: only the *latest field *from the /text:map/ list contains a
value.
To reformulate:
* if there are 3 fields in /text:map/, then during indexing the first
two are empty (let's name them 'text1' and 'text2') and the latest
field contains data (let's name it 'text3')
* if on the next attempt the field 'text3' is commented out, then
'text1' is empty and 'text2' contains data
Am 22.02.2019 um 15:01 schrieb Sorin Gheorghiu:
In addition:
* if there are 3 fields in /text:map/, then during indexing one
contains data (let's name it 'text1'), the others are empty (let's
name them 'text2' and 'text3'),
* if on the next attempt the field 'text1' is commented out, then
'text2' contains data and 'text3' is empty
-------- Weitergeleitete Nachricht --------
Betreff: Text Index build with empty fields
Datum: Fri, 22 Feb 2019 14:01:18 +0100
Von: Sorin Gheorghiu <[email protected]>
Antwort an: [email protected]
An: [email protected]
Hi,
When building the text index with the /jena.textindexer/ tool in Jena
3.10 for an external full-text search engine (Elasticsearch of course)
and having multiple fields with different names in /text:map/, just
*one field is indexed* (more precisely one field contains data, the
others are empty). It doesn't look to be an issue with Elasticsearch,
in the logs generated during the indexing the fields are already
missing the values, but one. The same setup worked in Jena 3.9.
Changing the Java version from 8 to 9 or 11 didn't change anything.
Could it be that changes of the new release have affected this tool
and we deal with a bug?
