javanna commented on issue #14485:
URL: https://github.com/apache/lucene/issues/14485#issuecomment-2892159524
Hey @jainankitk , I tried a few attempts, but did not get very far. I was
not able to put in enough time to put a proposal together and submit a PR yet.
I am happy to review changes
rmuir opened a new issue, #14687:
URL: https://github.com/apache/lucene/issues/14687
### Description
Some actions that run against `main`, e.g. on every push, nightly release
smoketest and other maintenance tasks. It would be nice if failures were sent
to `builds@` mailing list.
msfroh merged PR #14676:
URL: https://github.com/apache/lucene/pull/14676
--
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
rmuir commented on issue #14623:
URL: https://github.com/apache/lucene/issues/14623#issuecomment-2891731520
I agree with you, I dont want to slow anything down either.
But if we were to look at say, the last 10 file format changes as a sample
for analysis...
How many of these f
github-actions[bot] commented on PR #14686:
URL: https://github.com/apache/lucene/pull/14686#issuecomment-2891605156
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-check
label to it and you wil
ChrisHegarty opened a new pull request, #14686:
URL: https://github.com/apache/lucene/pull/14686
Specify and test that IOContext is immutable.
--
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
ChrisHegarty commented on issue #14623:
URL: https://github.com/apache/lucene/issues/14623#issuecomment-2891591535
Overall I would say that the Lucene project benefits a lot from these new
formats and the plethora of bug fixes and improvements in minor releases - I do
not want to change tha
rmuir commented on issue #14623:
URL: https://github.com/apache/lucene/issues/14623#issuecomment-2891433922
I don't know of any software that handles file formats as proposed, I don't
think it is the best solution and just adds complexity.
Along the same lines of "be careful what we b
uschindler commented on issue #14630:
URL: https://github.com/apache/lucene/issues/14630#issuecomment-2891445541
Hi,
> ```
> beast3:util.nightly[main]$ cat /proc/config.gz | gunzip | grep CONFIG_HZ
> # CONFIG_HZ_PERIODIC is not set
> # CONFIG_HZ_100 is not set
> # CONFIG_HZ
rmuir commented on issue #14630:
URL: https://github.com/apache/lucene/issues/14630#issuecomment-2891469123
I'm pretty sure it boils down to a compile-time macro.
For arch linux on mike's machine with many cores, easiest solution is to
switch to `linux-lts` kernel "with configuration
uschindler commented on issue #14630:
URL: https://github.com/apache/lucene/issues/14630#issuecomment-2891451314
Wah:
https://stackoverflow.com/questions/13427608/how-to-change-kernel-timer-frequency
--
This is an automated message from the Apache Git Service.
To respond to the message, p
stefanvodita merged PR #14685:
URL: https://github.com/apache/lucene/pull/14685
--
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...@lucen
github-actions[bot] commented on PR #14685:
URL: https://github.com/apache/lucene/pull/14685#issuecomment-2891436966
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-check
label to it and you wil
stefanvodita opened a new pull request, #14685:
URL: https://github.com/apache/lucene/pull/14685
Noticed the bot was commenting on draft PRs, which is probably not helpful.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub a
msokolov commented on issue #14399:
URL: https://github.com/apache/lucene/issues/14399#issuecomment-2891382202
> Would it make sense to have different collectors for the two cases, one
with and one without a cache?
--
This is an automated message from the Apache Git Service.
To respond to
msokolov commented on issue #14623:
URL: https://github.com/apache/lucene/issues/14623#issuecomment-2891377052
If we had a release policy that required format changes to be released in
isolation, would that have helped in this case? If we did that, you could at
least revert other (non forma
mikemccand commented on issue #14671:
URL: https://github.com/apache/lucene/issues/14671#issuecomment-2891105182
Oooh the nightly `knnPerfTest.py` benchy also noted a jump in `Visited Node
Count (K)` chart:
https://benchmarks.mikemccandless.com/knnResults.html#k_total_visited starting
2025
msokolov commented on issue #14671:
URL: https://github.com/apache/lucene/issues/14671#issuecomment-2890706274
performance seems to have recovered on
https://benchmarks.mikemccandless.com/PreFilteredVectorSearch.html but
@mikemccand have you reverted this whlle playing around with java vers
shubhamsrkdev commented on code in PR #14676:
URL: https://github.com/apache/lucene/pull/14676#discussion_r2095293465
##
lucene/core/src/test/org/apache/lucene/search/TestPointQueries.java:
##
@@ -2599,4 +2599,33 @@ public void
testPointInSetQuerySkipsNonMatchingSegments() thro
19 matches
Mail list logo
