Skip to content
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

Closed
elfisher opened this issue Apr 28, 2022 · 6 comments
Closed

[FEATURE] Update clients and tools compatibility matrix #533

elfisher opened this issue Apr 28, 2022 · 6 comments
Assignees
Labels
breaking Involves a breaking change to a release Closed - Complete Issue: Work is done and associated PRs closed enhancement New feature or request v2.0.0
Milestone

Comments

@elfisher
Copy link
Contributor

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.

@Naarcha-AWS
Copy link
Collaborator

@elfisher: Would this also be considered a breaking change?

@Naarcha-AWS Naarcha-AWS added the breaking Involves a breaking change to a release label May 4, 2022
@alicejw1
Copy link
Contributor

alicejw1 commented May 5, 2022

Hi @elfisher
Is there an alternative setting that they will use instead of the deprecated (in 1.x/removed in 2.0) setting?
Or is it ok to just remove all mentions of it?
Thanks

@alicejw1
Copy link
Contributor

alicejw1 commented May 5, 2022

i found a related ticket with related information : Remove Override #517

@alicejw1 alicejw1 removed the question label May 5, 2022
@alicejw1
Copy link
Contributor

alicejw1 commented May 5, 2022

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
https://opensearch.org/docs/latest/clients/index/

@alicejw1
Copy link
Contributor

alicejw1 commented May 5, 2022

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?

@alicejw1
Copy link
Contributor

alicejw1 commented May 5, 2022

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?
Thanks

@alicejw1 alicejw1 linked a pull request May 5, 2022 that will close this issue
@hdhalter hdhalter added this to the v2.0.0 milestone May 16, 2022
@hdhalter hdhalter added the Closed - Complete Issue: Work is done and associated PRs closed label Aug 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Involves a breaking change to a release Closed - Complete Issue: Work is done and associated PRs closed enhancement New feature or request v2.0.0
Projects
None yet
Development

No branches or pull requests

4 participants