-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to Lucene to 9.x #179
Comments
migrated to lucene-5.5.5 as a first step in 17babcd |
Migration to lucene-6.6.6 c5a44db merged in master. Now we can use multidimensional points. |
I'm resuming this work. It's harder than expected, because DocValues, used in lots of places, are not random accessible anymore since Lucene 7.0: |
- try to optimize memory usage of int[][] and long[][] arrays
Lucene 9.0.0 was recently released: https://lucene.apache.org/core/corenews.html#apache-lucenetm-900-available What other devs think about setting JDK 11 as minimum version for IPED, as it will use by default the embedded JDK 11 at processing and analysis time? Users won't have issues if they use the *.exe files and will receive a warning before exit if they execute the *.jar files with an older JDK version. |
I think that JDK 11 as minimum requirement is almost mandatory now. |
What JDK 11 feature/library would you like to use? |
…le anymore" This reverts commit f626f1b.
We are using a very old 4.9 version. A lot of Lucene APIs changed and it will need some work. This is a sensible upgrade and will break back compatibility. At least Lucene query performance and memory usage evolved a lot in 2018 and 2019: https://home.apache.org/~mikemccand/lucenebench/
TermQueries increased from 40/s to 1k/s !
The text was updated successfully, but these errors were encountered: