Re: How to create a local build that targets Java 11, when building with 17?

Apologies for not replying yesterday and thank you, Greg, for answering the question. All I could add is that it's a pretty common semantic versioning scheme [1], although there is no rigorous method of policing it - very often it's just relying on common sense. Lucene often does add big code

Re: Seeking Tools and Methods to Measure Lucene's Indexing Performance

Got it! Thanks! Ishan Chattopadhyaya 于2023年5月6日周六 12:19写道： > Check Lucene bench: https://home.apache.org/~mikemccand/lucenebench/ > > On Sat, 6 May, 2023, 9:30 am donghai tang, wrote: > >> Hello Lucene Community, >> >> I am in the process of learning about Lucene's indexing capabilities, and

Re: Seeking Tools and Methods to Measure Lucene's Indexing Performance

Check Lucene bench: https://home.apache.org/~mikemccand/lucenebench/ On Sat, 6 May, 2023, 9:30 am donghai tang, wrote: > Hello Lucene Community, > > I am in the process of learning about Lucene's indexing capabilities, and > I'm keen on conducting experiments to evaluate its performance.

Seeking Tools and Methods to Measure Lucene's Indexing Performance

Hello Lucene Community, I am in the process of learning about Lucene's indexing capabilities, and I'm keen on conducting experiments to evaluate its performance. However, I haven't come across any official tools specifically designed for measuring Lucene's indexing performance. I would be

Re: [VOTE] Release Lucene 9.6.0 RC2

(non-binding) +1 SUCCESS! [1:22:45.096774] Xugang https://www.amazingkoala.com.cn/ Nhat Nguyen 于2023年5月5日周五 06:23写道： > +1 > > SUCCESS! [0:54:22.989202] > > On Thu, May 4, 2023 at 2:07 PM Patrick Zhai wrote: > >> (non-binding) +1 >> SUCCESS! [0:47:50.033079] >> >> On Thu, May 4, 2023 at 1:27 

Re: TermInSetQuery: seekExact vs. seekCeil

Hi Greg IMO I still think the seekCeil is a better solution for the default posting format, as it could potentially save time on traversing the FST by doing the ping-pong skipping. I can see that in the case of using bloom filter the seekExact might be better but I'm not sure whether there is a

Re: How to create a local build that targets Java 11, when building with 17?

Hi Jonathan- The main branch is the tip of development, and what will eventually become 10.0. It can use a later version of Java, make (some) non-backwards-compatible API changes, etc. branch_9x tracks the latest 9.x release, and must run on the version of Java supported by 9.x releases, must be

TermInSetQuery: seekExact vs. seekCeil

Hi folks- Back in GH#12156 (https://github.com/apache/lucene/pull/12156), we rewrote TermInSetQuery to extend MultiTermQuery. With this change, TermInSetQuery can now leverage the various "rewrite methods" available to MultiTermQuery, allowing users to customize the query evaluation strategy

Re: How to create a local build that targets Java 11, when building with 17?

Thanks. What are the rules for what should go into main vs branch_9x? On Fri, May 5, 2023 at 1:54 PM Dawid Weiss wrote: > > The main branch is on Java 17, see build.gradle: > > // Minimum Java version required to compile and run Lucene. > minJavaVersion = JavaVersion.VERSION_17 > > Also,

Re: How to create a local build that targets Java 11, when building with 17?

The main branch is on Java 17, see build.gradle: // Minimum Java version required to compile and run Lucene. minJavaVersion = JavaVersion.VERSION_17 Also, don't use the default gradle task created by convention; use this one: ./gradlew mavenToLocal it's an alias but it publishes only a

Re: How to create a local build that targets Java 11, when building with 17?

Actually my hack doesn't work, the manifest file changes but the .class files do not. On Fri, May 5, 2023 at 12:38 PM Jonathan Ellis wrote: > `./gradlew publishToMavenLocal` gives me Java 17 class files by default, > which surprises me since AFAIK 11 is still the minimum to run Lucene. > > I

How to create a local build that targets Java 11, when building with 17?

`./gradlew publishToMavenLocal` gives me Java 17 class files by default, which surprises me since AFAIK 11 is still the minimum to run Lucene. I hacked it to work by editing javac.gradle sourceCompatibility = JavaVersion.VERSION_11 targetCompatibility = JavaVersion.VERSION_11 Is there a

Re: [VOTE] Release Lucene 9.6.0 RC2

PR is here: https://github.com/apache/lucene/pull/12265 Am 05.05.2023 um 11:48 schrieb Uwe Schindler: Hi, I let the smoker run with Policeman Jenkins, result is here: https://jenkins.thetaphi.de/job/Lucene-Release-Tester/26/console SUCCESS! [1:16:17.355285] I also did some manual checks,

Re: [VOTE] Release Lucene 9.6.0 RC2

Hi, I let the smoker run with Policeman Jenkins, result is here: https://jenkins.thetaphi.de/job/Lucene-Release-Tester/26/console SUCCESS! [1:16:17.355285] I also did some manual checks, especially for parts that I maintain: * Luke started fine with Java 11, Java 17, Java 19, Java 20. *