Re: [PR] build: replace six simple error prone checks [lucene]

2025-06-21 Thread via GitHub
github-actions[bot] commented on PR #14831: URL: https://github.com/apache/lucene/pull/14831#issuecomment-2993943716 This PR does not have an entry in lucene/CHANGES.txt. Consider adding one. If the PR doesn't need a changelog entry, then add the skip-changelog label to it and you will stop

[PR] build: replace six simple error prone checks [lucene]

2025-06-21 Thread via GitHub
rmuir opened a new pull request, #14831: URL: https://github.com/apache/lucene/pull/14831 Error-prone has many checks, but the tool doesn't scale well with respect to many checks: replace six (arbitrary) easy ones. ast-grep: * https://errorprone.info/bugpattern/SubstringOfZero *

Re: [PR] build: replace six simple error prone checks [lucene]

2025-06-21 Thread via GitHub
rmuir commented on code in PR #14831: URL: https://github.com/apache/lucene/pull/14831#discussion_r2160226517 ## lucene/test-framework/src/test/org/apache/lucene/tests/util/TestBeforeAfterOverrides.java: ## @@ -30,7 +30,9 @@ public TestBeforeAfterOverrides() { public static

Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene]

2025-06-21 Thread via GitHub
dweiss commented on PR #14764: URL: https://github.com/apache/lucene/pull/14764#issuecomment-2993509963 > whoa, `precommit` time is ~6 minutes, and test time is ~1.2 minutes I just realized that this is also an unfair comparison because that initial ```check -x test``` is compiling al

Re: [PR] Specialize `filterCompetitiveHits` when have exact 2 clauses [lucene]

2025-06-21 Thread via GitHub
HUSTERGS commented on PR #14827: URL: https://github.com/apache/lucene/pull/14827#issuecomment-2993494222 For what it's worth, the reason of this PR is that I find `filterCompetitiveHits` ocuppied about 13% of flamegraph on OrHighHigh query, ![image](https://github.com/user-attachments/

Re: [PR] Initial prototype of custom google java format tasks to replace spotless [lucene]

2025-06-21 Thread via GitHub
dweiss commented on PR #14824: URL: https://github.com/apache/lucene/pull/14824#issuecomment-2993523186 Fun. https://github.com/google/google-java-format/issues/1260 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

Re: [PR] Initial prototype of custom google java format tasks to replace spotless [lucene]

2025-06-21 Thread via GitHub
breskeby commented on code in PR #14824: URL: https://github.com/apache/lucene/pull/14824#discussion_r2159972822 ## build-tools/build-infra/src/main/java/org/apache/lucene/gradle/plugins/spotless/ParentGoogleJavaFormatTask.java: ## @@ -0,0 +1,69 @@ +package org.apache.lucene.gra

Re: [I] Integrate a JVector codec for KNN searches [lucene]

2025-06-21 Thread via GitHub
sam-herman commented on issue #14681: URL: https://github.com/apache/lucene/issues/14681#issuecomment-2993767101 > Things like Vamana or product quantization can definitely be useful, but from what I can tell, they offer similar properties to what we already have with HNSW + BBQ. jVe

Re: [PR] Specialize `filterCompetitiveHits` when have exact 2 clauses [lucene]

2025-06-21 Thread via GitHub
github-actions[bot] commented on PR #14827: URL: https://github.com/apache/lucene/pull/14827#issuecomment-2993476199 This PR does not have an entry in lucene/CHANGES.txt. Consider adding one. If the PR doesn't need a changelog entry, then add the skip-changelog label to it and you will stop

Re: [PR] Initial prototype of custom google java format tasks to replace spotless [lucene]

2025-06-21 Thread via GitHub
breskeby commented on code in PR #14824: URL: https://github.com/apache/lucene/pull/14824#discussion_r2159937021 ## build-tools/build-infra/src/main/java/org/apache/lucene/gradle/plugins/spotless/ParentGoogleJavaFormatTask.java: ## @@ -0,0 +1,69 @@ +package org.apache.lucene.gra

Re: [PR] Initial prototype of custom google java format tasks to replace spotless [lucene]

2025-06-21 Thread via GitHub
breskeby commented on code in PR #14824: URL: https://github.com/apache/lucene/pull/14824#discussion_r2159937021 ## build-tools/build-infra/src/main/java/org/apache/lucene/gradle/plugins/spotless/ParentGoogleJavaFormatTask.java: ## @@ -0,0 +1,69 @@ +package org.apache.lucene.gra

Re: [PR] Initial prototype of custom google java format tasks to replace spotless [lucene]

2025-06-21 Thread via GitHub
breskeby commented on PR #14824: URL: https://github.com/apache/lucene/pull/14824#issuecomment-2993428499 This is pretty cool. In elasticsearch we're also struggling with spotless and this looks like a good way forward, also reducing third party plugin dependencies which have proven to be b

Re: [PR] Initial prototype of custom google java format tasks to replace spotless [lucene]

2025-06-21 Thread via GitHub
dweiss commented on code in PR #14824: URL: https://github.com/apache/lucene/pull/14824#discussion_r2159970826 ## build-tools/build-infra/src/main/java/org/apache/lucene/gradle/plugins/spotless/ParentGoogleJavaFormatTask.java: ## @@ -0,0 +1,69 @@ +package org.apache.lucene.gradl

[I] Remove -XX:ActiveProcessorCount=1 from template.gradle.properties [lucene]

2025-06-21 Thread via GitHub
dweiss opened a new issue, #14829: URL: https://github.com/apache/lucene/issues/14829 ### Description I think this one does more harm than good, based on my observations here: https://github.com/apache/lucene/pull/14824#issuecomment-2993560243 I suggest we update the template

Re: [PR] Custom google java format tasks to replace spotless [lucene]

2025-06-21 Thread via GitHub
github-actions[bot] commented on PR #14824: URL: https://github.com/apache/lucene/pull/14824#issuecomment-2993562529 This PR does not have an entry in lucene/CHANGES.txt. Consider adding one. If the PR doesn't need a changelog entry, then add the skip-changelog label to it and you will stop

Re: [PR] docs: fix invalid html [lucene]

2025-06-21 Thread via GitHub
rmuir merged PR #14818: URL: https://github.com/apache/lucene/pull/14818 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apach

Re: [PR] [Build] Fix deprecation warning about automatic loading of test framework [lucene]

2025-06-21 Thread via GitHub
github-actions[bot] commented on PR #14828: URL: https://github.com/apache/lucene/pull/14828#issuecomment-2993519544 This PR does not have an entry in lucene/CHANGES.txt. Consider adding one. If the PR doesn't need a changelog entry, then add the skip-changelog label to it and you will stop

Re: [PR] Initial prototype of custom google java format tasks to replace spotless [lucene]

2025-06-21 Thread via GitHub
dweiss commented on code in PR #14824: URL: https://github.com/apache/lucene/pull/14824#discussion_r216564 ## build-tools/build-infra/src/main/java/org/apache/lucene/gradle/plugins/spotless/ParentGoogleJavaFormatTask.java: ## @@ -0,0 +1,69 @@ +package org.apache.lucene.gradl

Re: [I] Integrate a JVector codec for KNN searches [lucene]

2025-06-21 Thread via GitHub
sam-herman commented on issue #14681: URL: https://github.com/apache/lucene/issues/14681#issuecomment-2993725548 > I have a working JVector implementation for Lucene ported over from the opensearch implementation and I have benchmarks for that version. There are issues like pre-cached exact

Re: [PR] Custom google java format tasks to replace spotless [lucene]

2025-06-21 Thread via GitHub
rmuir commented on PR #14824: URL: https://github.com/apache/lucene/pull/14824#issuecomment-2993725482 The runners in use might not be beefy enough for larger sizing (gc threads, thread pools, etc) to help? -- This is an automated message from the Apache Git Service. To respond to the mes

Re: [PR] [Build] Fix deprecation warning about automatic loading of test framework [lucene]

2025-06-21 Thread via GitHub
dweiss merged PR #14828: URL: https://github.com/apache/lucene/pull/14828 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apac

[PR] Specialize `filterCompetitiveHits` when have exact 2 clauses [lucene]

2025-06-21 Thread via GitHub
HUSTERGS opened a new pull request, #14827: URL: https://github.com/apache/lucene/pull/14827 ### Description This PR propose to specialize function `filterCompetitiveHits` when we have exact 2 scorers, in order to reduce float calculation and potential function calls Luceneutil re

[PR] Optimize FieldExistsQuery to leverage index statistic in DocValuesSkipper [lucene]

2025-06-21 Thread via GitHub
bugmakerr opened a new pull request, #14830: URL: https://github.com/apache/lucene/pull/14830 ### Description -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment.

Re: [PR] Optimize FieldExistsQuery to leverage index statistic in DocValuesSkipper [lucene]

2025-06-21 Thread via GitHub
github-actions[bot] commented on PR #14830: URL: https://github.com/apache/lucene/pull/14830#issuecomment-2993596164 This PR does not have an entry in lucene/CHANGES.txt. Consider adding one. If the PR doesn't need a changelog entry, then add the skip-changelog label to it and you will stop

Re: [PR] [Build] Fix deprecation warning about automatic loading of test framework [lucene]

2025-06-21 Thread via GitHub
dweiss commented on PR #14828: URL: https://github.com/apache/lucene/pull/14828#issuecomment-2993693465 > But I'm afraid they keep the check and just fail. I think they shouldn't mess with extra arguments - maybe you can convince them so. It's similar to this issue - https://githu

Re: [PR] Custom google java format tasks to replace spotless [lucene]

2025-06-21 Thread via GitHub
dweiss commented on PR #14824: URL: https://github.com/apache/lucene/pull/14824#issuecomment-2993698382 With: ``` -Xmx1g -XX:ReservedCodeCacheSize=256m -XX:TieredStopAtLevel=1 ``` I get: ``` max-workers: 8 real 0m9.768s real 0m9.486s real 0m9.501s max-workers: 1

Re: [PR] Custom google java format tasks to replace spotless [lucene]

2025-06-21 Thread via GitHub
github-actions[bot] commented on PR #14824: URL: https://github.com/apache/lucene/pull/14824#issuecomment-2993699244 This PR does not have an entry in lucene/CHANGES.txt. Consider adding one. If the PR doesn't need a changelog entry, then add the skip-changelog label to it and you will stop

Re: [PR] Custom google java format tasks to replace spotless [lucene]

2025-06-21 Thread via GitHub
dweiss commented on PR #14824: URL: https://github.com/apache/lucene/pull/14824#issuecomment-2993704851 On gh runners changing these options seems to have no effect. * before removing ```-XX:TieredStopAtLevel=1 -XX:ActiveProcessorCount=1```: ![image](https://github.com/user-attachment

Re: [PR] Custom google java format tasks to replace spotless [lucene]

2025-06-21 Thread via GitHub
github-actions[bot] commented on PR #14824: URL: https://github.com/apache/lucene/pull/14824#issuecomment-2993705268 This PR does not have an entry in lucene/CHANGES.txt. Consider adding one. If the PR doesn't need a changelog entry, then add the skip-changelog label to it and you will stop

Re: [PR] Custom google java format tasks to replace spotless [lucene]

2025-06-21 Thread via GitHub
rmuir commented on PR #14824: URL: https://github.com/apache/lucene/pull/14824#issuecomment-2993683230 @dweiss maybe remove the parallelgc along with if you are testing. It's only needed because with 1 CPU ergonomics will default you to SerialGC which is too slow. -- This is an automated

Re: [PR] Initial prototype of custom google java format tasks to replace spotless [lucene]

2025-06-21 Thread via GitHub
dweiss commented on PR #14824: URL: https://github.com/apache/lucene/pull/14824#issuecomment-2993560243 Here are some benchmarks from my Linux system. This runs the patch with varying number of workers and the default ```-XX:ActiveProcessorCount=1``` in gradle.properties. This is a

Re: [PR] [Build] Fix deprecation warning about automatic loading of test framework [lucene]

2025-06-21 Thread via GitHub
breskeby commented on PR #14828: URL: https://github.com/apache/lucene/pull/14828#issuecomment-2993580446 it will be actually interesting how this will behave in gradle 9.0. Ideally it would just work as junit would be found on the module path in this case here. But I'm afraid they keep the

[PR] [Build] Fix deprecation warning about automatic loading of test framework [lucene]

2025-06-21 Thread via GitHub
breskeby opened a new pull request, #14828: URL: https://github.com/apache/lucene/pull/14828 ### Description This fixes deprecation warning "The automatic loading of test framework implementation dependencies has been deprecated." Gradle test tasks relies on having the test framework