Re: [JENKINS] Lucene-9.x-Windows (64bit/jdk-18) - Build # 1677 - Still Failing!

2022-12-30 Thread Patrick Zhai
My bad, when the fix I backported contains JDK17 API and so it can't build in 9x, I just pushed the fix for it, sorry! On Fri, Dec 30, 2022 at 5:01 PM Policeman Jenkins Server < jenk...@thetaphi.de> wrote: > Build: https://jenkins.thetaphi.de/job/Lucene-9.x-Windows/1677/ > Java: 64bit/jdk-18 -XX:

Re: Is there a way to customize segment names?

2022-12-30 Thread Vigya Sharma
Hi Patrick, This is an interesting question, and from what I understood, I see correctness problems in what you're trying to implement. Let me make sure I understand correctly... So indexer-1 created segments 1,2,3,4 and indexer-2 created segments 1', 2', 3', 4' independently (they just have the

Re: [JENKINS] Lucene-main-Linux (64bit/jdk-17.0.3) - Build # 39124 - Still Unstable!

2022-12-30 Thread Greg Miller
Ah, it does indeed. Thank you for the quick fix Patrick! Cheers, -Greg On Fri, Dec 30, 2022 at 10:01 AM Patrick Zhai wrote: > Seems related to the commit just pushed? I put a quick fix: > https://github.com/apache/lucene/pull/12049 > > On Fri, Dec 30, 2022 at 9:35 AM Policeman Jenkins Server <

Re: Is there a way to customize segment names?

2022-12-30 Thread Patrick Zhai
Hi Robert, got it, thanks! Hi Uwe, yes we do have a way to detect whether the segment is created by node A or B even if they share the same name, however, lucene does not allow such situation (same name but generated by different writer) when calling `openIfChanged` to try to incrementally load th

Re: [JENKINS] Lucene-main-Linux (64bit/jdk-17.0.3) - Build # 39124 - Still Unstable!

2022-12-30 Thread Patrick Zhai
Seems related to the commit just pushed? I put a quick fix: https://github.com/apache/lucene/pull/12049 On Fri, Dec 30, 2022 at 9:35 AM Policeman Jenkins Server < jenk...@thetaphi.de> wrote: > Build: https://jenkins.thetaphi.de/job/Lucene-main-Linux/39124/ > Java: 64bit/jdk-17.0.3 -XX:+UseCompres

Re: Request for naming help

2022-12-30 Thread Greg Miller
OK, great! Thanks Marc. I plan on merging the PR today. Cheers, -Greg On Thu, Dec 29, 2022 at 3:23 PM Marc D'Mello wrote: > Hi Greg, > > I'm also OK merging as is since this is a new feature and doesn't affect > any of the current functionality. I also think there are no glaring issues > with t

RE: Re: Integer.MAX_VALUE sentinel never checked?

2022-12-30 Thread santosh kumar
On 3203/12/01 19:23:01 Doug Cutting wrote: > I don't think this value actually find its way into the results. Rather > it causes PhraseScorer.score() to exit, as this value is always greater > than the value of 'end' passed into that method. > > Doug > > Simon Cozens wrote: > > > Plucene is nearly