Re: [PR] Use github wf to add module labels for PR based on file changes [lucene]

2025-02-02 Thread via GitHub
stefanvodita commented on PR #14101: URL: https://github.com/apache/lucene/pull/14101#issuecomment-2629498867 Thank you for this contribution @pseudo-nymous, I merged it just now and I'm really looking forward to see the first PR using it! -- This is an automated message from the Apache G

Re: [I] Create bot to label PRs based on the files they touch [lucene]

2025-02-02 Thread via GitHub
stefanvodita closed issue #13897: Create bot to label PRs based on the files they touch URL: https://github.com/apache/lucene/issues/13897 -- 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 specifi

Re: [PR] Use github wf to add module labels for PR based on file changes [lucene]

2025-02-02 Thread via GitHub
stefanvodita merged PR #14101: URL: https://github.com/apache/lucene/pull/14101 -- 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

Re: [PR] Use github wf to add module labels for PR based on file changes [lucene]

2025-02-02 Thread via GitHub
pseudo-nymous commented on PR #14101: URL: https://github.com/apache/lucene/pull/14101#issuecomment-2629507768 Thanks. I checked if same script could be used to label older PRs but there is no such event corresponding to already closed PR. Maybe we can write an individual script

Re: [PR] Use github wf to add module labels for PR based on file changes [lucene]

2025-02-02 Thread via GitHub
stefanvodita commented on PR #14101: URL: https://github.com/apache/lucene/pull/14101#issuecomment-2629513783 Brilliant! Let us know if you find anything. If you're interesting in this area of GitHub workflows / community tools, there are a few others that would be great to do: 1. #13898

Re: [PR] Use github wf to add module labels for PR based on file changes [lucene]

2025-02-02 Thread via GitHub
pseudo-nymous commented on PR #14101: URL: https://github.com/apache/lucene/pull/14101#issuecomment-2629515885 I'll be happy to work on these. Thanks! -- 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

Re: [PR] Filtered disjunctions may miss some top hits. [lucene]

2025-02-02 Thread via GitHub
jpountz merged PR #14186: URL: https://github.com/apache/lucene/pull/14186 -- 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.apa

Re: [PR] Introduce bpv24 vectorized decoding for DocIdsWriter [lucene]

2025-02-02 Thread via GitHub
iverase commented on PR #14176: URL: https://github.com/apache/lucene/pull/14176#issuecomment-2629385255 These numbers look great1 I want to run this change on the geo benchmarks but I expect similar speed ups. I am planning to do it early next week. One thing I am unhappy with is wit

Re: [I] Allow skip_factor to be set dynamically within QueryCache [lucene]

2025-02-02 Thread via GitHub
kkewwei commented on issue #14183: URL: https://github.com/apache/lucene/issues/14183#issuecomment-2629365142 In query-sensitive scenarios, the dataset is very small, there is ample remaining memory space. Users even want to cache all queries in memory, however this cannot be achieved due t