Avoid using deprecated Lucene APIs in internals
Description
100% Done
duplicates
Activity
Show:
Isen October 4, 2017 at 10:09 AM
That's awesome!
Can't wait for Hibernate 6!
Yoann Rodière October 4, 2017 at 8:38 AM
Thanks for the report, but this specific fix has already been implemented as part of HSEARCH-2811, and is present in the latest version of Hibernate Search (5.8.1.Final).
You can try again with Hibernate Search 5.8.1.Final, but be aware that we've never tested Hibernate Search with Lucene 6 and are planning on upgrading in Hibernate Search 6 only (we'll probably upgrade directly to Lucene 7).
Isen October 4, 2017 at 8:08 AM
When running with lucene >= 6.0.0 (till the lastest 7.0.0)
Runs just fine with lucene 5.5.4.
Deprecated Lucene method has been remove since Lucene-core 6.0.0. It says,
Documentation
Sanne Grinovero June 13, 2017 at 5:14 PM
Moving out of the 5.8.x release train: we've done many good steps already, there's no need to have them all.
Fixed
Details
Details
Assignee
Yoann RodièreReporter
Sanne GrinoveroSprint
None
Fix versions
Priority
MajorCreated April 8, 2016 at 12:19 PM
Updated July 31, 2020 at 1:15 PM
Resolved July 2, 2020 at 11:20 AM
Unless we expose the deprecated Lucene types on public APIs, we should stop using them.
There are several categories of such bad usage in the code base, so I'll create sub tasks to split this work up.
The test code needs to be polished as well, as the goal is to make it easier to eventually migrate to newer Lucene versions.