So, by using backwards codec jar :
Lucene 6.6.0 is now using older codec that comes with it, right?
Then, the latest codec is enforced to use by reindexing the data with new
Lucene 6.6.0 (due to switching from 6.1.0), right?
Thus, i did not need to rerun indexing because of use of backwards cod
How would a fixup API work? We would try to provide correctOffset
throughout the full analysis chain?
Mike McCandless
http://blog.mikemccandless.com
On Wed, Jul 25, 2018 at 8:27 AM, Michael Sokolov wrote:
> I've run into some difficulties with offsets in some TokenFilters I've been
> writing,
You would have to if you would e.g. still have had a Lucene50 Codec index
in use, even with 6.1.0.
This is not new that there is the backwards compatible jar which you need
to add if you want to use old codecs.
https://lucene.apache.org/core/6_2_0/backward-codecs/overview-summary.html
