-
Notifications
You must be signed in to change notification settings - Fork 141
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
unknown setting [archived.opendistro.sql.cursor.enabled] error when upgrading #136
Comments
This looks broken, the setting should have been deprecated and not removed? |
I renamed the issue as we do provide a backward compatible way to do this in other plugins, I think this is a bug in the SQL plugin where the setting should have been deprecated and not removed |
Yes, we will make it deprecated instead of removing. |
Tasks
|
One question, if we do want to remove the setting eventually, How could we do that? Does it means the customer to delete the archive settings during upgrade? The PR elastic/elasticsearch#28888 which archive the unknown and invalid settings. The PR callout that it allows the setting update to go through, and the archived settings can be removed at a later time. |
Is your feature request related to a problem? Please describe.
In SQL Plugin, the settings
opendistro.sql.cursor.enable
are deprecated and removed. We noticed that if those settings are configured before upgrade, they will be archived and seems block other cluster setting change after upgrade.Describe the solution you'd like
The OpenSearch should have the clearly way to handle the setting deprecation.
Describe alternatives you've considered
The clealry defined check list for customer which defined which they should do before rolling upgrade.
Additional context
opendistro.sql.cursor.enable
in SQL plugin.The text was updated successfully, but these errors were encountered: