Uwe,
This is beautiful! Especially for conversion from Trie to Point fields is
going to be extremely handy. I am going to have to check this out further.
Thank you for the tip!
Rahul
On Mon, Jan 17, 2022 at 10:23 AM Uwe Schindler wrote:
> By the way
> > Hi, one thing that always works to "force
By the way
> Hi, one thing that always works to "forcefully" upgrade without reindexing.
> You
> just merge the old index into a completely new index not by coping files, but
> by
> sending their SegmentReaders to addIndex, stripping all metadata from them
> with some trick:
> https://lucene.apac
i.de
> -Original Message-
> From: Rahul Goswami
> Sent: Wednesday, January 12, 2022 6:36 AM
> To: java-user@lucene.apache.org
> Subject: Re: Moving from lucene 6.x to 8.x
>
> Thanks Vinay for the link to Erick's talk! I hadn't seen it and I must
> admit it did
Thanks for the explanation Michael. I read more about term vectors and your
explanation in combination helps put things into perspective. .
On Thu, Jan 13, 2022 at 8:53 AM Michael Sokolov wrote:
> I think the "broken offsets" refers to offsets of tokens "going
> backwards". Offsets are attribute
I think the "broken offsets" refers to offsets of tokens "going
backwards". Offsets are attributes of tokens that refer back to their
byte position in the original indexed text. Going backwards means -- a
token with a greater position (in the sequence of tokens, or token
graph) should not have a le
Thanks Vinay for the link to Erick's talk! I hadn't seen it and I must
admit it did help put a few things into perspective.
I was able to track down the JIRAs (thank you 'git blame')
surrounding/leading up to this architectural decision and the linked
patches:
https://issues.apache.org/jira/browse
Hi Rahul,
I am not an expert so someone else might provide a better answer. However,
I remember
@Erick briefly talked about this restriction in one of his talks here:-
https://www.youtube.com/watch?v=eaQBH_H3d3g&t=621s (not sure if you have
seen it already).
As he explains, earlier it looked like
Hello,
Would appreciate any insights on the issue.Are there any backward
incompatible changes in 8.x index because of which the lucene upgrader is
unable to upgrade any index EVER touched by <= 6.x ? Or is the restriction
more of a safety net at this point for possible future incompatibilities ?
T
Hello,
I am using Apache Solr 7.7.2 with indexes which were originally created on
4.8 and upgraded ever since. I recently tried upgrading to 8.x using the
lucene IndexUpgrader tool and the upgrade fails. I know that lucene 8.x
prevents opening any segment which was touched by <= 6.x at any point in
