Will try on it.
Thanks Uwe :)
On Sat, May 6, 2017 at 4:02 AM, Uwe Schindler wrote:
> Hi Aravinth,
>
> To get rid of the partially merged (mixed) docvalues fields you can use
> the following additional approach on top of my previous mail:
>
> > Erick was referring to Solr. To fix your issue with
Hi Aravinth,
To get rid of the partially merged (mixed) docvalues fields you can use the
following additional approach on top of my previous mail:
> Erick was referring to Solr. To fix your issue without fully indexing you can
> use merging to update the whole index. To do this use the followin
Hi Aravinth,
Erick was referring to Solr. To fix your issue without fully indexing you can
use merging to update the whole index. To do this use the following approach:
Wrap your index using UninvertingReader. Then get all LeadReaders using the
leaves() method. Wrap all this leaves with SlowCod
Thanks Erick
On Fri, May 5, 2017 at 9:19 PM, Erick Erickson
wrote:
> In a word, "no". You must re-index from scratch. Worse, now that you
> have some segments thinking the fields are docValues and some not and
> maybe some mixed, I know of no way to un-entangle them.
>
> I'd create a new collect
In a word, "no". You must re-index from scratch. Worse, now that you
have some segments thinking the fields are docValues and some not and
maybe some mixed, I know of no way to un-entangle them.
I'd create a new collection and re-index it entirely, then use
collection aliasing to point the applica
Hi all,
On process of moving to Lucene 5 from Lucene 4, we faced this following
issue
We have enabled doc values in Lucene 5.we previously don't used doc values
in Lucene 4
Using UninvertingReader, sorting works fine until the first merge happens.
On merge documents in the older version without d