Re: Release Lucene 9.4.2

ys to improve the test situation? I > think > > >> >> we need to beef up checkindex to exercise seek() on the vectors, > also > > >> >> we need to look at static analysis to try to find other similar > bugs. > > >> >> This would help

Re: Backporting of Nori

Hello Roy and Shad, What you are asking is not straightforward, I worry it would take me a lot of time and I'm not even sure I would succeed, and I would assume that other committers who read your email felt the same way. My preferred path forward would be to delay support of Korean in Lucene.NET

Re: HNSW search with threshold

set k == Integer.MAX_VALUE. > > чт, 10 нояб. 2022 г. в 12:43, Adrien Grand : > >> I wonder if it would actually be a good idea to support filtering _only_ >> based on distance. In the worst case scenario, this may require traversing >> the whole HNSW graph and would r

Re: HNSW search with threshold

I wonder if it would actually be a good idea to support filtering _only_ based on distance. In the worst case scenario, this may require traversing the whole HNSW graph and would run in linear time with the number of vectors, with a high constant factor since we'd need to compute a distance for

Re: Dense union of doc IDs

I opened an issue to track this idea: https://github.com/apache/lucene/issues/11915 On Mon, Nov 7, 2022 at 1:21 PM LuXugang wrote: > +1 If we would have a new BulkAdder and it could detect long runs of set > bits, It also could be at least used in LRUQueryCache to cache part dense > docs

Re: Release Lucene 9.4.2

ind other similar bugs. > This would help prevent "whack-a-mole" and improve correctness going > forwards. > > I want to help more but it's difficult timing-wise, lots of stuff > going on this week, and in my country friday is Veteran's Day holiday. > > On Wed, Nov

Release Lucene 9.4.2

Hello all, A bad integer overflow has been discovered in the KNN vectors format, which affects segments that have more than ~16M vectors. I'd like to do a bugfix release when the bug is fixed and we have a test

Re: Dense union of doc IDs

to speed things up in case when index sorting is enabled as described in my previous email, and e.g. we could optimize counting hits or terms facets with such an index organization, but it's something we could evaluate separately. On Mon, Nov 7, 2022 at 12:05 PM Adrien Grand wrote: > I have b

Re: Dense union of doc IDs

I have been thinking about a similar feature for conjunctions and negations. When you have many low-cardinality fields, a good way to speed up queries on these fields is to configure an index sort on these fields. This automatically creates large gaps in postings between long runs of ones, and

Re: [VOTE] Release Lucene 9.4.1 RC1

+1 SUCCESS! [0:47:01.119384] On Thu, Oct 20, 2022 at 4:24 PM Ignacio Vera wrote: > Please vote for release candidate 1 for Lucene 9.4.1 > > > The artifacts can be downloaded from: > > > https://dist.apache.org/repos/dist/dev/lucene/lucene-9.4.1-RC1-rev-810817993e0956e63e29906e78a245949501b77d >

Welcome Luca Cavanna as Lucene committer

I'm pleased to announce that Luca Cavanna has accepted the PMC's invitation to become a committer. Luca, the tradition is that new committers introduce themselves with a brief bio. Congratulations and welcome! -- Adrien

Re: Missing tags for releases 8.8.2 thru 8.11.2

Ahhh thanks Dawid, this makes sense. On Tue, Oct 4, 2022 at 9:23 AM Dawid Weiss wrote: > > Tags seem to exist on the lucene-solr repository ( >> https://github.com/apache/lucene-solr) so maybe they were missed from >> the migration when we did the Lucene/Solr split? +Dawid Weiss >> I wonder if

Re: Missing tags for releases 8.8.2 thru 8.11.2

Tags seem to exist on the lucene-solr repository ( https://github.com/apache/lucene-solr) so maybe they were missed from the migration when we did the Lucene/Solr split? +Dawid Weiss I wonder if you have thoughts on this. On Tue, Oct 4, 2022 at 7:55 AM Shad Storhaug wrote: > I was just

Re: [VOTE] Release Lucene 9.4.0 RC3

+1 SUCCESS! [1:13:37.634770] On Tue, Sep 27, 2022 at 6:44 PM Uwe Schindler wrote: > Hi, > > Policeman Jenkins checked the release candidate 3 (RC3) for me ( > https://jenkins.thetaphi.de/job/Lucene-Release-Tester/22/console): > > SUCCESS! [1:42:45.782213] > Finished: SUCCESS > > I also checked

Re: [VOTE] Release Lucene 9.4.0 RC1

The change is now on branch_9_4. On Mon, Sep 26, 2022 at 2:38 PM Adrien Grand wrote: > I opened a PR and will backport it to relevant branches shortly: > https://github.com/apache/lucene/pull/11818. > > On Mon, Sep 26, 2022 at 2:26 PM Uwe Schindler wrote: > >> Hi Michael,

Re: [VOTE] Release Lucene 9.4.0 RC1

zip > 24.3 MiB/187.4 MiB downloaded > > So I can update and merge, build succeeds and it provisiones JDK 19 > automatically and Gradle runs. > > Uwe > > > On Mon, Sep 26, 2022 at 5:42 AM Adrien Grand wrote: > >> Ignacio made me notice than the new Lucene94FieldI

Re: [VOTE] Release Lucene 9.4.0 RC1

e Java 19 MMapDirectory as discussed > before. Everything is ready to merge! > > Uwe > Am 26.09.2022 um 11:42 schrieb Adrien Grand: > > Ignacio made me notice than the new Lucene94FieldInfosFormat did not > change the codec name compared to Lucene90FieldInfosFormat: > https://githu

Re: [VOTE] Release Lucene 9.4.0 RC1

>> wrote: >> >>> The smoke tests passed for me too.. >>> >>> >>> (no vote) >>> >>> SUCCESS! [1:12:31.588303] >>> >>> On Thu, Sep 22, 2022 at 2:27 AM Ignacio Vera wrote: >>> >>>> +1 >>>&g

Re: [VOTE] Release Lucene 9.4.0 RC1

+1 SUCCESS! [0:45:35.275017] On Wed, Sep 21, 2022 at 9:19 PM Michael McCandless < luc...@mikemccandless.com> wrote: > +1 > > > SUCCESS! [0:27:16.514391] > > > Mike McCandless > > http://blog.mikemccandless.com > > > On Wed, Sep 21, 2022 at 2:32 PM Dawid Weiss wrote: > >> >> +1. >> SUCCESS!

Re: Subject: New branch and feature freeze for Lucene 9.4.0

2022 at 6:24 AM Adrien Grand wrote: > >> Hi Mike, >> >> If you have not started a RC yet, I'd like to include some small fixes >> for bugs that were recently introduced in Lucene: >> - https://github.com/apache/lucene/pull/11792 >> - https://github.com/apache/l

Re: Subject: New branch and feature freeze for Lucene 9.4.0

what >>>>>> > was happening in the buggy case) and posted a fix today >>>>>> > https://github.com/apache/lucene/pull/11781. >>>>>> > >>>>>> > There are a couple of other outstanding issues I found while doing a >>>>

Re: Subject: New branch and feature freeze for Lucene 9.4.0

or Monday at the latest, > but if you can do the backport today or tomorrow, that's fine by me. > > On Thu, Sep 15, 2022 at 10:55 AM Adrien Grand wrote: > > > > Mike, I'm tempted to backport https://github.com/apache/lucene/pull/1068 > to branch_9_4, which is a bugfix that

Re: Subject: New branch and feature freeze for Lucene 9.4.0

Mike, I'm tempted to backport https://github.com/apache/lucene/pull/1068 to branch_9_4, which is a bugfix that looks pretty safe to me. What do you think? On Tue, Sep 13, 2022 at 4:11 PM Mayya Sharipova wrote: > Thanks for running more tests, Michael. > It is encouraging that you saw a similar

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

I could not reproduce the issue, which is worrying, but this looks like an actual issue. I opened a pull request: https://github.com/apache/lucene/pull/11726. On Sun, Aug 28, 2022 at 2:36 PM Policeman Jenkins Server < jenk...@thetaphi.de> wrote: > Build:

Welcome Vigya Sharma as Lucene committer

I'm pleased to announce that Vigya Sharma has accepted the PMC's invitation to become a committer. Vigya, the tradition is that new committers introduce themselves with a brief bio. Congratulations and welcome! -- Adrien

Re: New branch and feature freeze for Lucene 9.3.0

Thanks Ignacio! I tried to iterate on some release highlights to make them sound more exciting. On Mon, Jul 25, 2022 at 5:05 PM Ignacio Vera wrote: > Ignacio Vera > Jul 20, 2022, 1:41 PM (5 days ago) > to dev > Adrien told me that I sent the wrong link, I thought I could share the > draft

Re: [VOTE] Release Lucene 9.3.0 RC1

+1 SUCCESS! [0:54:33.954171] On Mon, Jul 25, 2022 at 1:12 PM Ignacio Vera wrote: > Please vote for release candidate 1 for Lucene 9.3.0 > > > The artifacts can be downloaded from: > > > https://dist.apache.org/repos/dist/dev/lucene/lucene-9.3.0-RC1-rev-d25cebcef7a80369f4dfb9285ca7360a810b75dc >

Re: Lucene 9.3.0 release

While I can understand the excitement about LUCENE-10592, it's also a big change, maybe we should not even try to get it in before cutting the branch? On Tue, Jul 19, 2022 at 4:09 PM Mayya Sharipova wrote: > Thanks for the reminder about the release, Ignacio! > About LUCENE-10592

Re: How to avoid double-emails on all git issue/PR updates?

Hey Mike, I'm only subscribed to issues/PRs I'm participating in on GitHub, which I've found useful since I can filter these and be more reactive on them, while still having access to the entire stream of activity via issues@l.a.o. On Sun, Jul 10, 2022 at 2:27 PM Michael McCandless <

Re: Finding out which fields matched the query

Uwe, Elasticsearch's named queries are not using a collector actually. Ater top hits have been evaluated for the whole query, they are evaluated independently on each of the top hits. It's probably faster than the collector approach since it doesn't add per-document overhead to collection, but

Re: A prototype migration tool Jira to GitHub

FWIW I don't mind receiving these one-time notifications for the purpose of the migration. On Fri, Jun 24, 2022 at 12:58 PM Tomoko Uchida wrote: > > If you could give me some "example mail", I can add a "feed to trash" > sieve rule before you start it. > > If we decide to migrate all Jira

Re: MergeTrigger consistency in MergePolicy "find merges"

methods. > > > Le lun. 20 juin 2022 à 14:26, Adrien Grand a écrit : > >> Wouldn't this be a bug in the AlwaysForceMergePolicy, which should return >> no merges if there is already a single segment with no deletes? >> >> On Mon, Jun 20, 2022 at 1:30

Re: MergeTrigger consistency in MergePolicy "find merges"

output of the first explicit forced > merge, and so on. For this degenerated AlwaysForceMergePolicy, the test > runs merges in an infinite loop. > > Le lun. 20 juin 2022 à 11:11, Adrien Grand a écrit : > >> You seem to imply that `forceMerge` runs a cascaded merge where the fir

Re: MergeTrigger consistency in MergePolicy "find merges"

You seem to imply that `forceMerge` runs a cascaded merge where the first merge creates some new segments that become inputs to a second merge. Have you considered running a single merge? We had a discussion about cascaded forced merges and TieredMergePolicy last year and ended up changing

Re: [JENKINS] Lucene-main-MacOSX (64bit/jdk-18) - Build # 8148 - Failure!

Thanks Gautam and sorry for taking so long to address these failures. It should be good now. On Wed, Jun 15, 2022 at 8:38 AM Gautam Worah wrote: > Hi folks, > > We've recently started seeing an increased number of failed builds, > especially on the >

Re: [RESULT] [VOTE] Migration to GitHub issue from Jira

Maybe a 3rd option could be to only use GitHub for new issues by adding some text to the Jira create issue dialog that says something like "JIRA is deprecated, please use GitHub for new issues" to encourage users to create new issues on GitHub instead of JIRA. On Wed, Jun 15, 2022 at 11:40 AM

Re: 30% query performance degradation for documents with small stored fields

t; I wonder whether it would be worth trying switching from stored fields >> to doc values. The access patterns are different, so the change would >> not be trivial, but you might be able to achieve gains this way - I >> really am not sure whether or not you would, the storage m

Re: [VOTE] Migration to GitHub issue from Jira (LUCENE-10557)

+1 (PMC) On Tue, Jun 7, 2022 at 9:09 AM Bruno Roustant wrote: > +0 (PMC) > > While I like the simplification, I'm a little concerned by the risk of > disruption in history. > > Le mar. 7 juin 2022 à 05:07, Tomoko Uchida > a écrit : > >> I'm sorry there was a mistake in the important date. This

Re: 30% query performance degradation for documents with small stored fields

Hi Alexander, Sorry that these changes impacted your workload negatively. We're trying to have sensible defaults for the performance/compression trade-off in the default codec, and indeed our guidance is to write a custom codec when it doesn't work. As you identified, Lucene only guarantees

Welcome Greg Miller to the Lucene PMC

I'm pleased to announce that Greg Miller has accepted an invitation to join the Lucene PMC! Congratulations Greg, and welcome aboard! -- Adrien

Welcome Lu Xugang as Lucene committer

I'm pleased to announce that Lu Xugang has accepted the PMC's invitation to become a committer. Xugang, the tradition is that new committers introduce themselves with a brief bio. Congratulations and welcome! -- Adrien

Welcome Chris Hegarty as Lucene committer

I'm pleased to announce that Chris Hegarty has accepted the PMC's invitation to become a committer. Chris, the tradition is that new committers introduce themselves with a brief bio. Congratulations and welcome! -- Adrien

Re: [VOTE] Release Lucene 9.2.0 RC2

+1 SUCCESS! [1:21:57.197735] I tested with Java 11 and Java 17. CHANGES look good too. On Thu, May 19, 2022 at 5:17 PM Alan Woodward wrote: > Please vote for release candidate 2 for Lucene 9.2.0 > > The artifacts can be downloaded from: > >

Re: [JENKINS] Lucene » Lucene-NightlyTests-main - Build # 642 - Unstable!

I pushed a fix for these TestIndexWriterMergePolicy.testMaxBufferedDocsChange failures. On Thu, May 19, 2022 at 8:20 AM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > Build: > https://ci-builds.apache.org/job/Lucene/job/Lucene-NightlyTests-main/642/ > > 1 tests failed. > FAILED: >

Re: Allow to directly link to GitHub PR from CHANGES?

Thanks Tomoko! I'm +1 on no longer requiring external contributors to create JIRA issues, JIRA can be quite intimidating the first time you have to deal with it with its complex UI, specific markup language, etc. This will hopefully improve the experience of first-time contributors. On Mon, May

Re: Release notes draft for Apache Solr 9.0

Maybe release notes could mention a few benefits that Solr gets automatically from Lucene 9 like the new analyzers and better space efficiency of postings thanks to PFOR? I also concur with Jason, I was expecting vector search to make the top line of the release notes? On Mon, Mar 28, 2022 at

Re: Lucene PMC Chair Bruno Roustant

Congratulations Bruno! On Wed, Mar 23, 2022 at 2:03 PM Michael Sokolov wrote: > > Hello, Lucene developers. Lucene Program Management Committee has > elected a new chair, Bruno Roustant, and the Board has approved. > Bruno, thank you for stepping up, and congratulations! > > -Mike > >

Re: [ANNOUNCE] Apache Lucene 9.1.0 released

Thanks Mike. I'm getting all the credit on this one because I sent the announcement, but Julie actually did all the hard work! Le mar. 22 mars 2022, 20:07, Michael Sokolov a écrit : > Thank you for another release Adrien! > > On Tue, Mar 22, 2022 at 10:32 AM Adrien Gra

Re: [VOTE] Release Lucene 9.1.0 RC2

> Adrien has agreed to take over as release manager in my absence I just completed the post-release steps, so everything should be good now. Please let me know if something looks odd. On Sun, Mar 20, 2022 at 9:07 PM Julie Tibshirani wrote: > > Hi everyone, I am headed out of town for a week

[ANNOUNCE] Apache Lucene 9.1.0 released

The Lucene PMC is pleased to announce the release of Apache Lucene 9.1.0. Apache Lucene is a high-performance, full-featured search engine library written entirely in Java. It is a technology suitable for nearly any application that requires structured search, full-text search, faceting,

[RESULT][VOTE] Release Lucene 9.1.0 RC2

It's been >72h since the vote was initiated and the result is: +1 9 (8 binding) 0 1 -1 0 This vote has PASSED. On Sun, Mar 20, 2022 at 9:07 PM Julie Tibshirani wrote: > > Hi everyone, I am headed out of town for a week without internet access. > Adrien has agreed to take over as release

Re: [VOTE] Release Lucene 9.1.0 RC2

Hi Anshum, Do you remember what the issues were on the first 4 attempts? Le jeu. 17 mars 2022, 19:50, Anshum Gupta a écrit : > Hi Julie, > > Thanks for volunteering as the RM. > > After 4 attempts, I finally got the smoke-tester (jdk11) to pass on the > 5th attempt. > > Tested out using some

Re: [VOTE] Release Lucene 9.1.0 RC2

+1 SUCCESS! [1:18:36.769572] On Thu, Mar 17, 2022 at 2:22 PM Nhat Nguyen wrote: > > Hi Mayya, > > You can safely ignore that test failure. It's a known issue: LUCENE-10088. > This issue is unlikely to happen outside our tests unless users set > IndexWriterConfig#maxBufferedDocs extremely low.

Re: [VOTE] Release Lucene 9.1.0 RC1

gt; I also unzipped the archives and verified Javadocs. Luke started with >> Windows and whitespace in path name. I was able to open an 8.x index from >> the backwards indexes. >> >> Unfortunately I had no time to do a real module system test with a project, >> b

Re: [VOTE] Release Lucene 9.1.0 RC1

+1 [1:15:46.282120] On Tue, Mar 15, 2022 at 3:19 PM Dawid Weiss wrote: > > > Could we change this propertyOrDefault() hack in Gradle to make -D have > > higher prio? > > Perhaps this wasn't explicit - yes, if you modify that method (and > propertyOrDefaultOrEnv) then you can control the

Re: Generate autocomplete predictions

Hi Adrien > > Thanks for your feedback! > > From a "project management" point of view how do I best do this? > > Should I just create a Pull Request with a first prototype, or discuss > the design first in Jira tickets? > > Thanks > > Michael > > &

Re: Generate autocomplete predictions

Hi Michael, This sounds like a good fit for Lucene to me. On Fri, Mar 11, 2022 at 11:15 PM Michael Wechner wrote: > > Hi > > I recently implemened auto-suggest based on > > https://lucene.apache.org/core/9_0_0/suggest/index.html > > whereas I am currently managing the terms / predictions (e.g.

Re: Lucene 9.1 release soon?

+1 On Thu, Feb 24, 2022 at 8:43 AM Michael Wechner wrote: > > I think this would be great :-) thank you very much for your efforts! > > Michael > > Am 24.02.22 um 00:28 schrieb Julie Tibshirani: > > Hello everyone, > > > > Would there be support for releasing Lucene 9.1 soon? It has been ~2.5 >

Welcome Guo Feng as Lucene committer

I'm pleased to announce that Guo Feng has accepted the PMC's invitation to become a committer. Feng, the tradition is that new committers introduce themselves with a brief bio. Congratulations and welcome! -- Adrien - To

Re: Question about max clause counts

is to use TermInSetQuery. I don't find this in > its docs, but what are its benefits - is it faster, or does it take less > memory? > > --Petko > > On Thu, Jan 13, 2022 at 1:10 AM Adrien Grand wrote: >> >> Hi Petko, >> >> We have been designing que

Re: Question about max clause counts

Hi Petko, We have been designing queries and the whole framework for query execution with the assumption in mind that queries would be reasonable, so it's hard to tell exactly what would break, but I think it's expected that queries wouldn't execute in the most efficient way, CPU-wise,

Re: Specializing FilterReaders with long-lived behaviour

Hi Nikola, I've been striving to keep the CacheKey constructor private in order to avoid performance bugs with reader wrappers that only exist for the lifetime of a single request, so I appreciate that you are thinking of options that guide users towards only creating custom cache keys on

Re: Heads up: main branch will soon require Java 17

I merged the PR that bumps the minimum required Java version to 17 earlier today. On Thu, Jan 6, 2022 at 4:40 PM Adrien Grand wrote: > > I confirmed that the Lucene-Check-main job now passes: > https://builds.apache.org/job/Lucene/job/Lucene-Check-main/. > > On Thu, Jan 6, 2022 a

Re: Heads up: main branch will soon require Java 17

it. >> Here it only loads 3 places and those in some un-intuitive order. >> >> Nevertheless, jobs are back enabled and you can merge. >> >> Uwe >> >> - >> Uwe Schindler >> Achterdiek 19, D-28357 Bremen >> https://www.thetaphi.de >> eMa

Re: Heads up: main branch will soon require Java 17

me > > > directory to setup node-specific values. As Gradle searches for all those > > > files > > > and applies them, the node-specific ones now only have the daemon disable > > > and the number of workers. Everything else I removed. > > > > > > S

Re: Heads up: main branch will soon require Java 17

gt; Uwe Schindler > Achterdiek 19, D-28357 Bremen > https://www.thetaphi.de > eMail: u...@thetaphi.de > > > -Original Message- > > From: Adrien Grand > > Sent: Thursday, January 6, 2022 11:28 AM > > To: Lucene Dev > > Subject: Re: Heads up: main

Re: Heads up: main branch will soon require Java 17

I just updated the gradle.properties file under "Config files" to add the module exports to JVM args, the next build should pass. On Thu, Jan 6, 2022 at 11:28 AM Adrien Grand wrote: > > To clarify, merging the PR wouldn't address the test failures. > > On Thu, Jan 6, 2

Re: Heads up: main branch will soon require Java 17

To clarify, merging the PR wouldn't address the test failures. On Thu, Jan 6, 2022 at 11:27 AM Adrien Grand wrote: > > This seems to be due to the fact that it's using an old > gradle.properties file that doesn't have the module exports that Dawid > added as part of LUCENE-10

Re: Heads up: main branch will soon require Java 17

This seems to be due to the fact that it's using an old gradle.properties file that doesn't have the module exports that Dawid added as part of LUCENE-10066. https://github.com/apache/lucene/pull/259/files#diff-fbdfae634c6898f4a415bc2a278ff771c38436d70b0e64250ab068b4b3e58426R48-R52 Let me look

Re: Heads up: main branch will soon require Java 17

st jdk-17 bugfix release, currently > it is GA release only. > > Uwe > > - > Uwe Schindler > Achterdiek 19, D-28357 Bremen > https://www.thetaphi.de > eMail: u...@thetaphi.de > > > -Original Message- > > From: Adrien Grand > > Sent: Thursday,

Re: [JENKINS] Lucene-Solr-8.11-MacOSX (64bit/jdk1.8.0) - Build # 164 - Still Unstable!

I just disabled 8.11 jobs on the ASF Jenkins. On Thu, Jan 6, 2022 at 9:33 AM Policeman Jenkins Server wrote: > > Build: https://jenkins.thetaphi.de/job/Lucene-Solr-8.11-MacOSX/164/ > Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseParallelGC > > 1 tests failed. > FAILED: >

Heads up: main branch will soon require Java 17

Hello all, I am about to bump the minimum required version to build Lucene from 11 to 17 on the main branch, ie. Lucene 10.0, so you won't be able to build Lucene unless JAVA_HOME points to a JDK 17. Here is the link to the PR for those interested: https://github.com/apache/lucene/pull/579. I

Re: Welcome Haoyu (Patrick) Zhai as Lucene Committer

Welcome Patrick! On Wed, Dec 22, 2021 at 5:04 PM Namgyu Kim wrote: > > Congratulations and welcome, Patrick! :D > > On Sun, Dec 19, 2021 at 6:12 PM Dawid Weiss wrote: >> >> Hello everyone! >> >> Please welcome Haoyu Zhai as the latest Lucene committer. You may also >> know Haoyu as Patrick -

Re: Lucene/Solr 8.11.1 release

Jan, if you remember the names of the tests that fail, can you annotate them with @BadApple so that they will not fail when building new RCs or future 8.11 patch releases? On Tue, Dec 14, 2021 at 8:41 AM Jan Høydahl wrote: > > I've had one run which passed tests, but then it failed signing due

[ANNOUNCE] Apache Lucene 9.0.0 released

The Lucene PMC is pleased to announce the release of Apache Lucene 9.0. Apache Lucene is a high-performance, full-featured search engine library written entirely in Java. It is a technology suitable for nearly any application that requires structured search, full-text search, faceting,

Re: Maven publication with the Gradle build

you need any > help. > > Dawid > > On Mon, Dec 6, 2021 at 2:19 PM Adrien Grand wrote: > > > > Hello, > > > > The release wizard still suggests using Ant for Maven publication: > > > > cd ~/.lucene-releases/9.0.0/lucene > > ant clean st

Maven publication with the Gradle build

Hello, The release wizard still suggests using Ant for Maven publication: cd ~/.lucene-releases/9.0.0/lucene ant clean stage-maven-artifacts \ -Dmaven.dist.dir=~/.lucene-releases/9.0.0/RC4/dist/lucene-9.0.0-RC4-rev-0b18b3b965cedaf5eb129aa41243a44c83ca826d/lucene/maven \

[RESULT][VOTE] Release Lucene 9.0.0 RC4

It's been >72h since the vote was initiated and the result is: +1 11 (10 binding) 0 1 -1 0 This vote has PASSED. On Mon, Dec 6, 2021 at 10:15 AM Adrien Grand wrote: > > Thanks Uwe for finding this issue. I agree with your and Tomoko's > judgement that it doesn't need to

Re: [VOTE] Release Lucene 9.0.0 RC4

> > > > > Everything else looks fine, in the documentation we unfortunately did not > > > merge the index.html changes (they are only in 9.x) to show correct path > > > of > > > Luke to start it. > > > > > > +/-0 to release (so don't count a vo

Re: Bump minimum Java version to 17 on main (10.0)

I opened https://issues.apache.org/jira/browse/LUCENE-10283. On Fri, Nov 5, 2021 at 3:46 AM Robert Muir wrote: > > On Thu, Nov 4, 2021 at 10:42 AM Dawid Weiss wrote: > > > > > we don't have to "support" users on our main trunk branch. That's why > > > we make releases. > > > > Nah. I don't

Re: [VOTE] Release Lucene 9.0.0 RC4

Thanks Anshum, Dawid and others for the support! Le jeu. 2 déc. 2021 à 20:39, Dawid Weiss a écrit : > > SUCCESS! [0:17:10.950384] > > +1. > > Sorry for all the extra work, Adrien. > > Dawid > > On Wed, Dec 1, 2021 at 5:56 PM Adrien Grand wrote: > >&

[VOTE] Release Lucene 9.0.0 RC4

Please vote for release candidate 4 for Lucene 9.0.0 The artifacts can be downloaded from: https://dist.apache.org/repos/dist/dev/lucene/lucene-9.0.0-RC4-rev-0b18b3b965cedaf5eb129aa41243a44c83ca826d You can run the smoke tester directly with this command: python3 -u

Welcome Julie Tibshirani to the Lucene PMC

I'm pleased to announce that Julie Tibshirani has accepted an invitation to join the Lucene PMC! Congratulations Julie, and welcome aboard! -- Adrien

Re: [VOTE] Release Lucene 9.0.0 RC3

't respin just to get this fix, but if we're going to anyway, it > would be nice to grab it. > > Here's a PR to do so if the group thinks it makes sense: > https://github.com/apache/lucene/pull/495 > > Cheers, > -Greg > > On Mon, Nov 29, 2021 at 2:02 PM Adrien Grand wrot

Re: [VOTE] Release Lucene 9.0.0 RC3

You could send a heads up to dev@ to make this more visible but I don't think we need a vote. Thanks Uwe and Dawid for taking care of this. Le lun. 29 nov. 2021 à 22:25, Uwe Schindler a écrit : > Hi, > > Dawid and I changed the gradle build to change the module names to be > according to

[RESULT][VOTE] Release Lucene 9.0.0 RC3

starting from main. We can extract these instructions into a >> >> > separate document. On the other hand, it wouldn't be shown up there >> on >> >> > github front-page then... and times have changed - this is where most >> >> > folks would probably end up rea

Re: Anyone familiar (or use) MultiRangeQuery?

7). > > It seems to me that this is in fact a bug, so I'd suggest we move > forward with fixing it. But if anyone disagrees, let's discuss :) > > Cheers, > -Greg > > On Thu, Nov 25, 2021 at 9:47 AM Adrien Grand wrote: > > > > I think Greg is right and this

[VOTE] Release Lucene 9.0.0 RC3

Please vote for release candidate 3 for Lucene 9.0.0. The artifacts can be downloaded from: https://dist.apache.org/repos/dist/dev/lucene/lucene-9.0.0-RC3-rev-1ddce848cf3d5067efcafc6569d5f8203e56af0b You can run the smoke tester directly with this command: python3 -u

[RESULT][VOTE] Release Lucene 9.0.0 RC2

This vote has failed. I'll create a new RC. On Fri, Nov 26, 2021 at 2:50 PM Adrien Grand wrote: > > +1 Thanks Tomoko. > > On Fri, Nov 26, 2021 at 10:51 AM Tomoko Uchida > wrote: >> >> Hi, >> >> I think all Luke-related blockers or issues were resolved

Re: [VOTE] Release Lucene 9.0.0 RC2

> Thanks, > Tomoko > > > 2021年11月26日(金) 2:29 Adrien Grand : > >> Sorry Tomoko I'm just seeing your message now. Please go ahead and >> backport to branch_9_0. >> >> On Thu, Nov 25, 2021 at 12:41 PM Tomoko Uchida < >> tomoko.uchida.1...@gmai

Re: Anyone familiar (or use) MultiRangeQuery?

I think Greg is right and this query is supposed to be a specialization for a disjunction of multiple range queries. It helps because you need to visit the index of the BKD tree and build a bit set once for the entire disjunction instead of once per range. I suspect that the fact that it doesn't

Re: [VOTE] Release Lucene 9.0.0 RC2

or message which >> is >> >> > fatal! >> >> > >> >> > So -1 to release (sorry, we need a test with whitespace, e.g. >> smoketester should >> >> > check this, but starting luke is hard inside smoker). >> >> > >> >> >

Re: [VOTE] Release Lucene 9.0.0 RC2

solr-9.0.0, too  > > Uwe > > - > Uwe Schindler > Achterdiek 19, D-28357 Bremen > https://www.thetaphi.de > eMail: u...@thetaphi.de > > > -Original Message- > > From: Adrien Grand > > Sent: Tuesday, November 23, 2021 9:40 AM > > To: Lucene Dev &g

Re: What should we do of branch_8x?

I went ahead and merged the above PR, which wiped out the comment of branch_8x: https://github.com/apache/lucene-solr/tree/branch_8x. I also removed the 8.x builds on Apache Jenkins (which were only disabled until now). On Tue, Nov 23, 2021 at 7:52 PM Adrien Grand wrote: > I opened a

Re: What should we do of branch_8x?

ation stored? This file was there also to protect >> branches from writing (at least in github): >> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-BranchProtection >> > >> > Uwe >> > >> > - >

Re: What should we do of branch_8x?

gt;>>> - add a single ivy.xml there that refers to all lucene jars of 8.11.x > >>>>> (latest) > >>>>> - adapt solr's "copy-lucene-jars" ant task to copy the ivy output dir > >>>>> - delete the lucene stuff from release wiz

[FAILED][VOTE] Release Lucene 9.0.0 RC1

Thank you Tomoko. This vote has failed. I started a new vote for a RC2 that includes the fix for the Luke launch script. On Mon, Nov 22, 2021 at 2:11 PM Tomoko Uchida wrote: > > Ok, thank you. I backported it to branch_9_0. > > Tomoko > > 2021年11月22日(月) 21:29 Adrien Grand : &g

[VOTE] Release Lucene 9.0.0 RC2

Please vote for release candidate 2 for Lucene 9.0.0 The artifacts can be downloaded from: https://dist.apache.org/repos/dist/dev/lucene/lucene-9.0.0-RC2-rev-95072f3b71e67e308d71a6149323bf7dd04c8f75 You can run the smoke tester directly with this command: python3 -u

Re: [VOTE] Release Lucene 9.0.0 RC1

tch - but wanted to give notice > > of that, just in case. > > > > [1] > https://github.com/apache/lucene/commit/4193bcbc02313c82afcf8cf9e2d14e47466cb1c3 > > > > Tomoko > > > > 2021年11月22日(月) 6:18 Adrien Grand : > > > > > > Fair en

Re: What should we do of branch_8x?

.4711. > >> >> >> >> > >> >> >> >> As said before: let's close branch 8.x and add protection to > it in GitHub. Anybox may merge Bugfixes directly from Solr or Lucene main I > to branch_8_11. I see no problem. Just no index changes!

<    1   2   3   4   5   6   7   8   9   10   >