I managed to speed up my native implementation over lucene from 10% to ~35%
by adding bulk scoring:
https://github.com/mccullocht/lucene-knn-oxide/pull/1
I tested it with and without prefetching -- it's about 10% faster with
prefetching -- but I think much of the benefit comes from loading the que
Thank you for the thorough explanation! My idea in questioning this
was purely in trying to understand why it is the way it is. There is
not any problem as far as I know -- it just seemed strange to me that
we are compiling with jdk24 yet we have a special folder for
jdk24-only features (my interpr
You're right - there are still some out there.
On Wed, Jul 9, 2025 at 3:14 PM Uwe Schindler wrote:
> Oh I missed that one. Did we also remove all "catch SecurityException", I
> have the feeling I saw one yesterday.
>
> Uwe
> Am 09.07.2025 um 15:00 schrieb Dawid Weiss:
>
>
> +1.
>
>
>>- clean
Oh I missed that one. Did we also remove all "catch SecurityException",
I have the feeling I saw one yesterday.
Uwe
Am 09.07.2025 um 15:00 schrieb Dawid Weiss:
+1.
* cleanup of all
AccessController/SecurityManager/SecurityException (to be
done, will open PR soon
T
+1.
>- cleanup of all AccessController/SecurityManager/SecurityException
>(to be done, will open PR soon
>
>
This is already done, I think.
https://github.com/apache/lucene/pull/14801
D.
>
Hi,
as you might have followed by talk at BerlinBuzzwords
(https://2025.berlinbuzzwords.de/session/state-of-native-access-in-apache-lucene/,
https://www.youtube.com/watch?v=4RxkahnUBvg), I'd like to make the
proposal to release Lucene 11 with Java 25 in November or December this
year.
The d
Hi,
in theory we can't (see above), because there are some problems with
java compiler as the main sources are compiled with "-release 24", but
the incubator is not part of official API and this gets problematic (as
unstable). To ensure that our main classes get all checks by the
compiler and
