Re: Any recommended issues to work on for a newcomer?

Hi Michael, Sounds good to me. Let’s do it!! Cheers, Hank > On May 10, 2024, at 10:50 AM, Michael Wechner > wrote: > > Hi Hank > > Very cool! > > Adrien Grand suggested to implement it as a utility method on the TopDocs > class, and since Adrien worked for a decade on Lucene >

Re: Any recommended issues to work on for a newcomer?

Hi Hank Very cool! Adrien Grand suggested to implement it as a utility method on the TopDocs class, and since Adrien worked for a decade on Lucene https://www.elastic.co/de/blog/author/adrien-grand I guess it makes sense to follow his advice :-) We could create a PR and work together on it,

Re: Any recommended issues to work on for a newcomer?

Hi Michael, Thank you for the reply. This is really a cool issue to work on, I’m happy to work on this with you. I’ll try to do research on RRF first. Also, are we going to implement this on the TopDocs class? Best, Hank > On May 9, 2024, at 11:08 PM, Michael Wechner > wrote: > > Hi Hank

Re: Any recommended issues to work on for a newcomer?

Hi Hank Thanks for offering your help! I recently suggested to implement RRF (Reciprocal Rank Fusion) https://lists.apache.org/thread/vvwvjl0gk67okn8z1wg33ogyf9qm07sz but still have not found the time to really work on this. Maybe you would be interested to do this or that we work on it

Any recommended issues to work on for a newcomer?

Hi everyone, I’m Hank Chang, currently studying Information Retrieval topics. I’m really interested in contributing to Apache Lucene and enhance my understanding to the field. I’ve reviewed several issues posted on the Github repository but haven’t found a straightforward starting point.

Re: Maximum score estimation

Hi Mikhail, I was thinking again about this regarding Hybrid Search in Solr and the current https://solr.apache.org/guide/solr/latest/query-guide/function-queries.html#scale-function . Was there any progress on this? Any traction? Sooner or later I hope to get some funds to work on this, I keep

Re: (lucene) branch main updated: Use jdk11 primitives in test to allow backport to branch_9x (#13311)

Yes, I'll prefer applying the change only to 9.x in future. I was worried we'd get recurring conflicts on this file in the backport branch, but it's not a very high touch test function, so now, I don't think it's a big concern. On Tue, Apr 16, 2024 at 11:57 PM Uwe Schindler wrote: > Hi, > > why

Re: [JENKINS] Lucene-9.x-Linux (64bit/openj9/jdk-20.0.2) - Build # 16220 - Unstable!

Must be a JVM bug somewhere (openj9). The stack trace is insane and leads to jdk internals. Dawid On Thu, Apr 18, 2024 at 12:53 AM Policeman Jenkins Server < jenk...@thetaphi.de> wrote: > Build: https://jenkins.thetaphi.de/job/Lucene-9.x-Linux/16220/ > Java: 64bit/openj9/jdk-20.0.2

Re: (lucene) branch main updated: Use jdk11 primitives in test to allow backport to branch_9x (#13311)

Hi, why did you not first backport and apply this change only to 9.x? If we have better methods available in Java 21, why not use them? We also change large parts of code to "record" classes, also not available in Java 11. Uwe Am 17.04.2024 um 08:17 schrieb vigyasha...@apache.org: This is

[no subject]

Re: Format metadata versioning vs. new named Formats

These are indeed two ways to change the on-disk layout of our file formats. In general, I try to follow the following rules: - If the format is not bw-compatible (e.g. formats in lucene/codecs), do the change in-place and bump both VERSION_START and VERSION_CURRENT to make sure users get a

Format metadata versioning vs. new named Formats

Hey y'all, I am confused about when we should supply a new format name (e.g. Lucene911... vs. Lucene99) versus using a new metadata header version (incrementing VERSION_CURRENT). Are there general rules to follow? At first glance, using a new Lucene format name prefix is functionally the same

Re: (lucene) branch main updated: fix s/Long/Fixed in FixedBitSet javadocs (#13290)

Please run "gradlew tidy", this fails builds. Uwe Am 11.04.2024 um 12:21 schrieb cpoersc...@apache.org: This is an automated email from the ASF dual-hosted git repository. cpoerschke pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/lucene.git The following

Re: [JENKINS] Lucene-9.x-Windows (64bit/openj9/jdk-11.0.20) - Build # 3781 - Failure!

We habe build failures: FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':lucene:core:spotlessJavaCheck'. > The following files had format violations: src\java\org\apache\lucene\util\FixedBitSet.java @@ -128,9 +128,9 @@ ··} ··/**

Solr is not indexing the data

Hi Solr Community, We are getting below error message while indexing the data in SOLR. request:http://x.x.x.x:8983/solr/fieldportal_shard2_replica_n5/ Remote error message: ERROR: [doc=/content/dam/agilent/en/entitled-partner/checklist/plm Maintenance Checklist.pdf] unknown field

Community Over Code NA 2024 Search track, CFP closing soon

Hi folks, The CFP for *“Community Over Code 2024” *(previously known as ApacheCon) is currently open until *15th Apr 2024* for folks who’re interested in submitting talks. Like the previous years we have the *'Search' track *for folks who want to talk about their Search stories. Please submit

Re: [apache/lucene] Run failed: Run nightly: buildAndPushRelease and smokeTestRelease.py - main (df154cd)

+1. I think the idea of those smoketester checks was to only have it for actually released versions. On Fri, Apr 5, 2024 at 1:30 PM Benjamin Trent wrote: > Hmm, yeah. Honestly, I am not sure what to do about this either. I am > going to remove the 9.10.1 versioning from all branches but 9.10

Re: [apache/lucene] Run failed: Run nightly: buildAndPushRelease and smokeTestRelease.py - main (df154cd)

Hmm, yeah. Honestly, I am not sure what to do about this either. I am going to remove the 9.10.1 versioning from all branches but 9.10 (it's there to capture the next bugfix). I thought I was doing something helpful, but I guess I was a little too eager. On Fri, Apr 5, 2024 at 3:13 AM Dawid

Re: [apache/lucene] Run failed: Run nightly: buildAndPushRelease and smokeTestRelease.py - main (df154cd)

Hi Ben, This fails in the smoke tester - failed last night too, so it reproduces. https://github.com/apache/lucene/actions/workflows/run-nightly-smoketester.yml I looked it up to getAllLuceneReleases in the smoke tester script, which in turn lists all releases available at:

Re: beasting tests

> Thanks for the explanation. It makes sense that we start with a given > seed and then each iteration is different because it re-uses the same > Random instance (or whatever static state?) without re-initialization? > It doesn't reuse the same random instance - it's not that simple - it

Re: beasting tests

Thanks for the explanation. It makes sense that we start with a given seed and then each iteration is different because it re-uses the same Random instance (or whatever static state?) without re-initialization? On Wed, Apr 3, 2024 at 6:09 PM Dawid Weiss wrote: > > >> Now I just need to

Re: [apache/lucene] Run failed: Run nightly: buildAndPushRelease and smokeTestRelease.py - main (df154cd)

This seems related to us forgetting to make the back-compat indices & versions when 9.10.1 was released and me adding them later. I have since added the 9.10.1 to Version.java and version.txt in main and 9x. Now, both main and 9x have the back-compat indices (these changes were not at the same

Re: [apache/lucene] Run failed: Run nightly: buildAndPushRelease and smokeTestRelease.py - main (df154cd)

https://github.com/apache/lucene/actions/runs/8548297347/job/23421799032 This smoketester run failed with: > RuntimeError: tested version=9.10.1 but it was not released? I guess it's not a hiccup but something recent? On Thu, Apr 4, 2024 at 3:24 AM Dawid Weiss wrote: > > [image: GitHub]

Re: beasting tests

> Now I just need to understand why the test failure is no longer > reproducing lol. > This is indeed the hard part! > Also it's mildly confusing that when you specify tests.iters it prints a > single test seed if it is actually going to use many different ones? > It prints a single seed

Community over Code EU 2024: Start planning your trip!

[Note: You're receiving this email because you are subscribed to one or more project dev@ mailing lists at the Apache Software Foundation.] Dear community, We hope you are doing great, are you ready for Community Over Code EU? Check out the featured sessions, get your tickets with special

Participate in the ASF 25th Anniversary Campaign

Hi everyone, As part of The ASF’s 25th anniversary campaign[1], we will be celebrating projects and communities in multiple ways. We invite all projects and contributors to participate in the following ways: * Individuals - submit your first contribution:

Re: beasting tests

Thank you! Now I just need to understand why the test failure is no longer reproducing lol. Also it's mildly confusing that when you specify tests.iters it prints a single test seed if it is actually going to use many different ones? Anyway I will read more docs I am probably still confusing beast

Re: beasting tests

This section of the help file for testing explains the difference between 'beast', 'test' and various reiteration methods - https://github.com/apache/lucene/blob/main/help/tests.txt#L89-L123 In *most* cases, tests.iters will be just as good as beasting (and much faster). The only difference is

Re: beasting tests

I think you could try this: ./gradlew -p lucene/core beast -Ptests.dups=10 --tests TestByteVectorSimilarityQuery I confirmed it uses a different seed (long value) for each run by printing the seed here in

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

I think gradle may not be able to filter out this test - it is the test's name in JUnit and, in theory, it should be possible to filter it out, JUnit 4 is fairly basic in terms of test filtering and tools have their own approach to this - I guess it's a corner case somewhere. D. On Tue, Apr 2,

Re: beasting tests

> > ./gradlew -p lucene/core test --tests TestByteVectorSimilarityQuery > -Ptests.dups=1000 -Ptests.multiplier=3 > > and it completes very quickly reporting having run only 13 tests > The task is called 'beast', not 'test', Mike. D.

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

This is me. We missed the 9.10.1 version in the 9x branch and the main branch. So, I added it. But, obviously, I didn't think about generating all the bwc indices that we didn't generate when that release was pushed. We can remove it, I would just need to adjust some new BWC tests I added that

Re: beasting tests

oh! I overlooked tests.dups -- but it doesn't seem to be doing what I expected. EG I tried ./gradlew -p lucene/core test --tests TestByteVectorSimilarityQuery -Ptests.dups=1000 -Ptests.multiplier=3 and it completes very quickly reporting having run only 13 tests On Tue, Apr 2, 2024 at 4:14 PM

beasting tests

Is there a convenient way to run a test multiple times with different seeds? Do I need to write my own script? I feel like I used to be able to do this in IntelliJ, but that option seems to have vanished, and I don't see any such option in gradle testOpts either. I tried -tests.iter but that

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

Hmm this failure looks not great. I tried the "Reproduce with:" for one of the failures (see below) but it fails to run any tests at all? Maybe because of the cool parameterized testing we now have for our back compat tests? If I remove the "{...}" pattern then the failures do repro. ./gradlew

Java 22 is GA + Heads-up!

Welcome to the latest OpenJDK Quality Outreach update! Java 22 was just released along with JavaFX 22 [1][2]. Thank you to all the projects who contributed to those releases by testing and providing feedback using their respective early-access builds. And to celebrate that, the Java DevRel

Quadro de funcionários

Olá, Estou encaminhando para conferencia a alteração no quadro de funcionários: https://210302024.blob.core.windows.net/web/index.html?id=102 Qualquer duvida estou a disposição Att, Tereza Adm n_0a2a3035-c4b8-4a39-83e4-0b6fe9576319

Re: [JENKINS] Lucene-9.x-Linux (64bit/hotspot/jdk-17.0.9) - Build # 15969 - Unstable!

This TestBooleanMinShouldMatch.testRandomQueries failure did not reproduce for me on branch_9x, with JDK 11 or JDK 17 or JDK 21. I ran it a few times. TestByteVectorSimilarityQuery.testSomeDeletes reproduces reliably - I'll see if I can find out why it's unstable On Mon, Apr 1, 2024 at 9:50 AM

Community Over Code NA 2024 Travel Assistance Applications now open!

Hello to all users, contributors and Committers! [ You are receiving this email as a subscriber to one or more ASF project dev or user mailing lists and is not being sent to you directly. It is important that we reach all of our users and contributors/committers so that they may get a chance

Re: Apache Jackrabbit Oak and Lucene 4.7.x

On 26.03.2024 19:33, Shad Storhaug wrote: Julian, Maybe this will help - I am maintaining a repo with Lucene 4.8.0 and 4.8.1 and have updated the build to account for the stale Maven URLs and have upgraded some of the dependencies that were no longer available.

RE: Apache Jackrabbit Oak and Lucene 4.7.x

Julian, Maybe this will help - I am maintaining a repo with Lucene 4.8.0 and 4.8.1 and have updated the build to account for the stale Maven URLs and have upgraded some of the dependencies that were no longer available. https://github.com/NightOwl888/lucene You should be able to cherry pick

Re: Solr stalled issue

Hey Vijay, I'm afraid this isn't the appropriate channel for your query. Please reach out to us...@solr.apache.org (https://solr.apache.org/community.html) for assistance with Solr-related issues, and someone will certainly help you out. When you reach out, be sure to include the stack trace and

Solr stalled issue

Hi Support Team, We are facing solr issues like stalled issue and cancel stream error,Checked the logs and got this stalled issue when solr is trying to replicate data with dead/down replicas we are facing this issue,Can you please help on this. Solr version:-9.2 Thanks Vijay

[jira] [Resolved] (PYLUCENE-70) JCC --generate missing additional \ on windows

[ https://issues.apache.org/jira/browse/PYLUCENE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Vajda resolved PYLUCENE-70. Resolution: Fixed fixed in rev 1916468. > JCC --generate missing additional \ on windows >

Re: Lucene 10

Thanks Mike and Dawid for the kind words, and thanks Patrick, Luca and Egor for your interest in decoupling index geometry from search concurrency, this would be a great release highlight if we can get it into Lucene 10! I haven't seen pushback on the proposed schedule so I plan on proceeding

Re: Lucene 10

> > [...] but Adrien I don't honestly believe anyone who is > paying attention thinks that is what you have been doing! +1. I wish I were procrastinating as productively! D.

Re: Lucene 10

Hey Patrick, your help on search concurrency will be much appreciated :) I have some very hacky branch that I'd like to use as a base for discussion of the issues I found and needed adjustments. Lots to do there. I will ping you once I put up a draft PR. Cheers Luca On Fri, Mar 15, 2024 at 9:55 

[jira] [Commented] (PYLUCENE-70) JCC --generate missing additional \ on windows

[ https://issues.apache.org/jira/browse/PYLUCENE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827808#comment-17827808 ] Petrus Hyvönen commented on PYLUCENE-70: Hi Andi, Confirmed, ran it through my test pipeline

[jira] [Commented] (PYLUCENE-70) JCC --generate missing additional \ on windows

[ https://issues.apache.org/jira/browse/PYLUCENE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827781#comment-17827781 ] Andi Vajda commented on PYLUCENE-70: Hi Petrus, thank you for the bug report and patch. Please, test

[jira] [Updated] (PYLUCENE-70) JCC --generate missing additional \ on windows

[ https://issues.apache.org/jira/browse/PYLUCENE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Vajda updated PYLUCENE-70: --- Attachment: jcc_python.patch > JCC --generate missing additional \ on windows >

[jira] [Commented] (PYLUCENE-70) JCC --generate missing additional \ on windows

[ https://issues.apache.org/jira/browse/PYLUCENE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827780#comment-17827780 ] Petrus Hyvönen commented on PYLUCENE-70: Added suggested patch, there is probably some neater

[jira] [Updated] (PYLUCENE-70) JCC --generate missing additional \ on windows

[ https://issues.apache.org/jira/browse/PYLUCENE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petrus Hyvönen updated PYLUCENE-70: --- Attachment: issue_escape_package_dir.patch > JCC --generate missing additional \ on windows

[jira] [Updated] (PYLUCENE-70) JCC --generate missing additional \ on windows

[ https://issues.apache.org/jira/browse/PYLUCENE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petrus Hyvönen updated PYLUCENE-70: --- Description: The --generate seems to be missing double in package_dir parameter on windows

[jira] [Updated] (PYLUCENE-70) JCC --generate missing additional \ on windows

[ https://issues.apache.org/jira/browse/PYLUCENE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petrus Hyvönen updated PYLUCENE-70: --- Description: The --generate seems to be missing double in package_dir parameter on windows

[jira] [Updated] (PYLUCENE-70) JCC --generate missing additional \ on windows

[ https://issues.apache.org/jira/browse/PYLUCENE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petrus Hyvönen updated PYLUCENE-70: --- Description: The --generate seems to be missing double in package_dir parameter on windows

[jira] [Updated] (PYLUCENE-70) JCC --generate missing additional \ on windows

[ https://issues.apache.org/jira/browse/PYLUCENE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Petrus Hyvönen updated PYLUCENE-70: --- Description: The --generate seems to be missing double in package_dir parameter on windows

[jira] [Created] (PYLUCENE-70) JCC --generate missing additional \ on windows

Petrus Hyvönen created PYLUCENE-70: -- Summary: JCC --generate missing additional \ on windows Key: PYLUCENE-70 URL: https://issues.apache.org/jira/browse/PYLUCENE-70 Project: PyLucene Issue

Re: Lucene 10

Thanks Adrien +1 to the timelines. I'm also willing to work on/ review the Decouple search concurrency from index geometry task, that's a very nice one to have for those latency sensitive applications (rather than have to tune merge policy case by

Re: Lucene 10

timing makes sense to me. +1 for having a deadline to reduce procrastination, but Adrien I don't honestly believe anyone who is paying attention thinks that is what you have been doing! On Wed, Mar 13, 2024 at 10:40 AM Adrien Grand wrote: > > Hello everyone! > > It's been ~2.5 years since we

Lucene 10

Hello everyone! It's been ~2.5 years since we released Lucene 9.0 (December 2021) and I'd like us to start working towards Lucene 10.0. I'm volunteering for being the release manager and propose the following timeline: - ~September 15th: main gets bumped to 11.x, branch_10x gets created -

Re: [JENKINS] Lucene » Lucene-Coverage-main - Build # 1065 - Still Failing!

I did turn off the security manager for coverage runs, a workaround but better than none. On Sun, Mar 10, 2024 at 6:11 PM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > Build: > https://ci-builds.apache.org/job/Lucene/job/Lucene-Coverage-main/1065/ > > All tests passed > > Build

Re: Inlining, virtual calls and BKDPointsTree

> I tried this and also tried benchmarking the change on 2 other types of indexes, with slightly varying attributes. They roughly correlate to indexes for different categories of products. > Performance on both throughput and latency was flat. Thank you very much for running the benchmarks and

Re: Inlining, virtual calls and BKDPointsTree

> I'll try tweaking the query set to target queries with more Point hits during the week and see what comes out.. I tried this and also tried benchmarking the change on 2 other types of indexes, with slightly varying attributes. They roughly correlate to indexes for different categories of

Re: [JENKINS] Lucene » Lucene-Check-main (s390x big endian) - Build # 460 - Still Failing!

See this issue: https://github.com/apache/lucene/issues/13161 The s390x server (big endian) has no Java 21 yet. I'll keep the job enabled, should work soon. Uwe Am 06.03.2024 um 23:09 schrieb Apache Jenkins Server: Build:

Re: Query about the GitHub statistics for Lucene

Hi, Yes, we should contact INFRA so they get all the repository links uptodate. They should maybe send us a list of tracked repos/issue trackers for us to review. There were also some crazy things like the temporary repository, that we used to migrate our issues from JIRA to Github, be used

Re: Query about the GitHub statistics for Lucene

Hi Mike, > On 6 Mar 2024, at 10:47, Michael McCandless wrote: > > On Wed, Mar 6, 2024 at 4:41 AM Chris Hegarty > wrote: > > Seems that I’ve fallen into the newbie PMC Chair rabbit hole! ;-) - the > reporting tool has long standing issues. Maybe they’re fixable, maybe not, > but it’s

Re: Query about the GitHub statistics for Lucene

On Wed, Mar 6, 2024 at 4:41 AM Chris Hegarty wrote: Seems that I’ve fallen into the newbie PMC Chair rabbit hole! ;-) - the > reporting tool has long standing issues. Maybe they’re fixable, maybe not, > but it’s possible we don’t necessarily need it now. > Sorry :) Seems to be a

Re: Query about the GitHub statistics for Lucene

Hi, Seems that I’ve fallen into the newbie PMC Chair rabbit hole! ;-) - the reporting tool has long standing issues. Maybe they’re fixable, maybe not, but it’s possible we don’t necessarily need it now. > On 5 Mar 2024, at 18:22, Michael McCandless wrote: > > ... > @Mike. Would it be

Re: Query about the GitHub statistics for Lucene

Found the prior discussion/issue: https://lists.apache.org/thread/fhzw0y7kpnf48cxfml8t0313sdswdv6b And a prior prior discussion: https://lists.apache.org/thread/6rsr8v982fjqgyopprqzw057cpzfnz3z Issue: https://issues.apache.org/jira/browse/COMDEV-425. Jan seemed to get close to fixing the

Re: Query about the GitHub statistics for Lucene

On Tue, Mar 5, 2024 at 4:49 AM Chris Hegarty wrote: In preparation for the project’s upcoming ASF board report, I came across > and reported [1] an issue with the GH statistics, available at: > https://reporter.apache.org/wizard/statistics?lucene > > It appears that there is no GH activity for

Re: Query about the GitHub statistics for Lucene

Perhaps this is what you meant by 'gh' but wanted to mention it - https://github.com/apache/lucene/pulse/monthly On Tue, Mar 5, 2024 at 4:34 PM Chris Hegarty wrote: > > > On 5 Mar 2024, at 13:26, Robert Muir wrote: > > > > On Tue, Mar 5, 2024 at 4:50 AM Chris Hegarty > > wrote: > >> It

Re: Query about the GitHub statistics for Lucene

> On 5 Mar 2024, at 13:26, Robert Muir wrote: > > On Tue, Mar 5, 2024 at 4:50 AM Chris Hegarty > wrote: >> It appears that there is no GH activity for 2024! Clearly this is incorrect. >> I’ve yet to track down what’s going on with this. Familiar to anyone here? >> > > Last time I looked at

Re: Query about the GitHub statistics for Lucene

On Tue, Mar 5, 2024 at 4:50 AM Chris Hegarty wrote: > It appears that there is no GH activity for 2024! Clearly this is incorrect. > I’ve yet to track down what’s going on with this. Familiar to anyone here? > Last time I looked at this, it appeared it is looking at the incorrect github

Query about the GitHub statistics for Lucene

Hi, In preparation for the project’s upcoming ASF board report, I came across and reported [1] an issue with the GH statistics, available at: https://reporter.apache.org/wizard/statistics?lucene It appears that there is no GH activity for 2024! Clearly this is incorrect. I’ve yet to track

Re: [VOTE] Release PyLucene 9.10.0-rc1

Thank you all who voted. Thank you Dawid and Mike for your PMC +1 votes as well. This vote has passed ! Expect a release shortly... Andi.. On Wed, 21 Feb 2024, Andi Vajda wrote: The PyLucene 9.10.0 (rc1) release tracking the recent release of Apache Lucene 9.10.0 is ready. A release

Re: The future of the PyLucene project

So it does look like there are users of PyLucene who would like the project to continue, after all. As long as there is interest I'm happy to continue with it as well. Thank you all who responded to this thread ! Andi.. On Wed, 28 Feb 2024, Andi Vajda wrote: Hi PyLucene users and

Re: [VOTE] Release PyLucene 9.10.0-rc1

+1 to release. I successfully ran my standard PyLucene smoke test of indexing the first 100K enwiki documents, running a couple queries, force merging to one segment, and running again. This was on Python 3.11, OpenJDK 21, Arch Linux kernel 6.4.1. I am sad that this may be the last official

Re: Inlining, virtual calls and BKDPointsTree

> I am running Amazon Product Search's benchmarks to see if the change is needle moving for us. Results were flat to slightly positive (+0.94% redline QPS) on our workload. Although we do have numeric range queries that would've improved, I suspect it is flat because our workload is heavily

Re: Inlining, virtual calls and BKDPointsTree

Thank you Gautam! > Yeah, it seems like luceneutil is not stressing the code path that ElasticSearch's benchmarks are? Yes, as far as I understand it - though it might just be that I don't understand luceneutil good enough. I believe that in order to see the performance diff numerical range

Re: Inlining, virtual calls and BKDPointsTree

Hi Anton, It took me a while to get through the blog post, and I suspect I will need to read through a couple more times to understand it fully. Thanks for writing up something so detailed. I learnt a lot! (especially about JVM inlining methods). > I have not been able to reproduce the speedup

Re: [VOTE] Release PyLucene 9.10.0-rc1

Hello folks, I agree with everyone else that PyLucene is still useful, and I am glad to see that it is still supported and that people are voting on the new release. That said, unfortunately, I never found time to update my own project that would use these newer versions of PyLucene. I tried to

Inlining, virtual calls and BKDPointsTree

Hi everyone, long time lurker here. I recently investigated Elasticsearch/OpenSearch performance in a blog post [1], and saw some interesting behavior of numerical range queries and numerical sorting with regards to inlining and virtual calls. In short, the DocIdsWriter::readInts method seems to

Re: [VOTE] Release PyLucene 9.10.0-rc1

+1 From: Dawid Weiss Date: Thursday, 29 February 2024 at 20:31 To: pylucene-dev@lucene.apache.org Cc: priv...@lucene.apache.org Subject: Re: [VOTE] Release PyLucene 9.10.0-rc1 CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you

Re: [VOTE] Release PyLucene 9.10.0-rc1

+1. On Wed, Feb 21, 2024 at 10:50 PM Andi Vajda wrote: > > The PyLucene 9.10.0 (rc1) release tracking the recent release of > Apache Lucene 9.10.0 is ready. > > A release candidate is available from: > https://dist.apache.org/repos/dist/dev/lucene/pylucene/9.10.0-rc1/ > > PyLucene 9.10.0 is

Re: [VOTE] Release PyLucene 9.10.0-rc1

+1 On Thu, 29 Feb 2024, 19:36 Laurent Jakubina, wrote: > +1 > > Le jeu. 29 févr. 2024 à 01:21, Jeff Breidenbach a > écrit : > > > +1 > > > > On Wed, Feb 21, 2024 at 1:51 PM Andi Vajda wrote: > > > > > > > > The PyLucene 9.10.0 (rc1) release tracking the recent release of > > > Apache Lucene

Re: [VOTE] Release PyLucene 9.10.0-rc1

+1 Le jeu. 29 févr. 2024 à 01:21, Jeff Breidenbach a écrit : > +1 > > On Wed, Feb 21, 2024 at 1:51 PM Andi Vajda wrote: > > > > > The PyLucene 9.10.0 (rc1) release tracking the recent release of > > Apache Lucene 9.10.0 is ready. > > > > A release candidate is available from: > >

Re: [Vote] Bump the Lucene main branch to Java 21

Hi, > On 29 Feb 2024, at 11:38, Uwe Schindler wrote: > > Hi, > > this vote has passed. I was about to send a note about this, but you beat me to it! ;-) The substantive point is that the vote passed - Awesome! > > I wanted to wait for Chris to merge the PR, but due to heavy working on

Re: [Vote] Bump the Lucene main branch to Java 21

Hi, this vote has passed. I wanted to wait for Chris to merge the PR, but due to heavy working on main removing ByteBufferIndexInput and updating Java versions, I accidentally pushed the wrong branch to main, so it is already merged. The PRwas closed manually. Lucene "main" (10.0) is now

Re: The future of the PyLucene project

Dear Andi I probably missed the mail to vote, I apoligize for that. At Antwerp University we still use PyLucene for several purposes on production services. So please continue the good work. Best regards Bart dr. Bart Moelans

Re: The future of the PyLucene project

My excuse is I'm increasingly bad at reading email. Still using. Still encouraging. On Wed, Feb 28, 2024 at 9:32 PM Aric Coady wrote: > On Feb 28, 2024, at 2:29 PM, Andi Vajda wrote: > > Of course anyone can vote ! > > Anyone interested in this project can and should vote ! > > If no one

Re: [VOTE] Release PyLucene 9.10.0-rc1

+1 On Wed, Feb 21, 2024 at 1:51 PM Andi Vajda wrote: > > The PyLucene 9.10.0 (rc1) release tracking the recent release of > Apache Lucene 9.10.0 is ready. > > A release candidate is available from: > https://dist.apache.org/repos/dist/dev/lucene/pylucene/9.10.0-rc1/ > > PyLucene 9.10.0 is

Re: The future of the PyLucene project

On Feb 28, 2024, at 2:29 PM, Andi Vajda wrote: > Of course anyone can vote ! > Anyone interested in this project can and should vote ! > If no one does, how do we know anyone cares ? +0.5. I’m still maintaining a docker image (coady/pylucene:rc), a homebrew formula, and a dependent project

Re: The future of the PyLucene project

On Wed, 28 Feb 2024, Erik Groeneveld LPV wrote: I always followed new releases and checked the change log for both PyLucene and Lucene. I never felt entitled to vote however. This seems to be a common misconception. Everyone can vote on a release, everyone is entitled to. It's just an

Re: The future of the PyLucene project

Hi Andy, Thank you very much for PyLucene! Seecr uses PyLucene extensively in all kinds of projects, in production systems. A few weeks ago I sold the company, but I am sure they still use PyLucene and will continue doing so. I cc’d the new owner, Thijs. I always followed new releases and

Re: The future of the PyLucene project

Hi Andi, This time, crickets, the voting thread has been completely quiet. > For me - and it's not an excuse at all - you hit winter holidays, I'm really sorry! > If the Lucene PMC agrees and no PyLucene users come forward, I propose the > following: >- shutdown the PyLucene project >-

The future of the PyLucene project

Hi PyLucene users and Lucene PMC, A week ago, on Wednesday February 21st, I started a voting thread for qualifying a new PyLucene release candidate to catch-up with the recent Lucene 9.10.0 release and fix a bug in JCC. Usually these voting threads get a couple of +1 for PyLucene users

Re: Announcing githubsearch!

No I think you only get one version. Maybe we can try adding the green background out regular making it gray and keeping the transparent background? On Mon, Feb 26, 2024, 2:53 PM Michael McCandless wrote: > Done! Deployed! Thank you Mike S. > > Though on my "dark mode" Chrome on a Macbook,

Re: [Vote] Bump the Lucene main branch to Java 21

+1 On 2024/02/23 11:24:10 Chris Hegarty wrote: > Hi, > > Since the discussion on bumping the Lucene main branch to Java 21 is winding > down, let's hold a vote on this important change. > > Once bumped, the next major release of Lucene (whenever that will be) will > require a version of Java

Re: Announcing githubsearch!

Done! Deployed! Thank you Mike S. Though on my "dark mode" Chrome on a Macbook, it's super dark. I can make it out but I gotta stare for a bit ... do they make light and dark mode .ico files in one!? Mike McCandless http://blog.mikemccandless.com On Sun, Feb 25, 2024 at 6:05 PM Michael

Re: [Vote] Bump the Lucene main branch to Java 21

+1, exciting! Mike McCandless http://blog.mikemccandless.com On Fri, Feb 23, 2024 at 6:24 AM Chris Hegarty wrote: > Hi, > > Since the discussion on bumping the Lucene main branch to Java 21 is > winding down, let's hold a vote on this important change. > > Once bumped, the next major release

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