I am in process of upgrading ES from 0.20.2 to 1.3.4. Below are two
requests to test an analyzer / filter, and although the mapping files are
semantically the same the results are slightly different.
Can anyone provide some insight as to why the differ (the start_offest,
end_offset and position) ? Also does it matter ? The reason I noticed
this is because I'm trying to debug some unexpected behaviour with a query
where the result set for "a" are same for "aa" or even "axxxxxxxxxx".
We fixed EdgeNGram tokenizer / filter in the 1.x series but don't ask me
when exactly I think it was lucene 4.4 or so. Those offsets are now correct
while they where broken before.
not sure if this helps you to debug your problem
On Thursday, November 6, 2014 1:31:22 PM UTC+1, Ben George wrote:
I am in process of upgrading ES from 0.20.2 to 1.3.4. Below are two
requests to test an analyzer / filter, and although the mapping files are
semantically the same the results are slightly different.
Can anyone provide some insight as to why the differ (the start_offest,
end_offset and position) ? Also does it matter ? The reason I noticed
this is because I'm trying to debug some unexpected behaviour with a query
where the result set for "a" are same for "aa" or even "axxxxxxxxxx".
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.