-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[Deprecate] Setting explicit version on analysis component #1978
[Deprecate] Setting explicit version on analysis component #1978
Conversation
Lucene 9 removes the ability to define an explicit version on an analysis component. The version parameter is deprecated at parse time and a warning is issued to the user through the deprecation logger. Signed-off-by: Nicholas Walter Knize <[email protected]>
Can one of the admins verify this patch? |
Signed-off-by: Nicholas Walter Knize <[email protected]>
Another #1957 failure unrelated to this PR. Adding to #1715
|
start gradle check |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
minor question though same as on the other PR #1981 - which release we plan to deprecate this?
1.3. I'll backport to 1.x and open a removal PR to remove in main. |
…h-project#1978) Lucene 9 removes the ability to define an explicit version on an analysis component. The version parameter is deprecated at parse time and a warning is issued to the user through the deprecation logger. Signed-off-by: Nicholas Walter Knize <[email protected]>
…1985) Lucene 9 removes the ability to define an explicit version on an analysis component. The version parameter is deprecated at parse time and a warning is issued to the user through the deprecation logger. Signed-off-by: Nicholas Walter Knize <[email protected]>
Lucene 9 removes the ability to define an explicit version on an analysis component. In this PR the version parameter for an analysis component is deprecated at parse time and a warning issued to the user through the deprecation logger. A separate PR will completely remove the parameter in 2.0.0