On Sat, Nov 11, 2017 at 7:09 AM, Krishnamurthy, Kannan
wrote:
> Never mind my previous question, understood what you meant about the impact
> to norms after
> looking at the uses of CreatedMajorVersion in various Similarity classes. It
> almost looks
> re-indexing is the only option here. This w
n
From: Michael McCandless
Date: Friday, November 10, 2017 at 6:41 AM
To: Lucene Users , "Krishnamurthy, Kannan"
Subject: Re: Lucene 6.1.0 index upgrade
OK I'm sorry but I think you'll have to re-index; e.g. how norms are
computed and stored in the index
urthy, Kannan"
Subject: Re: Lucene 6.1.0 index upgrade
OK I'm sorry but I think you'll have to re-index; e.g. how norms are computed
and stored in the index has changed, which means even if you could somehow copy
or merge the index over to the new version, the norms would
OK I'm sorry but I think you'll have to re-index; e.g. how norms are
computed and stored in the index has changed, which means even if you could
somehow copy or merge the index over to the new version, the norms would be
incorrect.
Mike McCandless
http://blog.mikemccandless.com
On Thu, Nov 9, 20
Hi Mike,
It doesn’t work either, it throws “Cannot merge a segment that has been created
with major version 6 into this index which has been created by major version 7"
message. Let me try it after an upgrade as well. Same code below,
@Test
public void mergeUsingCodecReader()
Maybe try the addIndexes method that takes CodecReader[] instead? It will
be somewhat slower, since it fully reads and writes the index, but it
should work across major versions?
Mike McCandless
http://blog.mikemccandless.com
On Thu, Nov 9, 2017 at 3:59 PM, Krishnamurthy, Kannan <
kannan.krishn
Greetings.
We are currently using Lucene 6.1.0, our typical index size is ~ 200GB and we
are planning to move to Lucene 7.0.0.
Our daily indexing workflow currently uses IndexWriter.addIndexes() to add an
index(this will be on Lucene 7.0.0) to a copy of the of the 200GB index.
Further it cal
