-
Notifications
You must be signed in to change notification settings - Fork 507
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
[FEATURE] Update clients and tools compatibility matrix #533
Comments
@elfisher: Would this also be considered a breaking change? |
Hi @elfisher |
i found a related ticket with related information : Remove Override #517 |
Need info: where can i find out what isn't currently accurate on this list? Will look thru all linked bugs, but if anyone knows answer, please post here. thanks |
another question: do we need to update all 1.x doc sets to note this is deprecated? Or is it sufficient to just remove it from the 2.0 doc version? |
Hi @VachaShah, could you help me identify any of the items on this index page There is a list of legacy clients and tools - could you help me identify granularly which ones on this list will work with 2.0 (now that the setting is removed)? Or, if it's all of them, is it ok in your opinion to give a generic note that none of them will work with 2.0? |
Is your feature request related to a problem?
compatibility.override_main_response_version: true
was deprecated in OpenSearch 1.x and is being removed in 2.0. This will impact what legacy clients and other tools are compatible with OpenSearch 2.0 since it will not be able to use this setting.At a minimum, it will impact the following pages:
What solution would you like?
We should update these pages to reflect what will and will not be compatible with OpenSearch 2.0.
The text was updated successfully, but these errors were encountered: