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

Planned Breaking Changes for 2.0 #1780

Closed
Tracked by #1624 ...
brijos opened this issue Mar 18, 2022 · 8 comments
Closed
Tracked by #1624 ...

Planned Breaking Changes for 2.0 #1780

brijos opened this issue Mar 18, 2022 · 8 comments
Labels
campaign Parent issues of OpenSearch release campaigns. enhancement New Enhancement

Comments

@brijos
Copy link

brijos commented Mar 18, 2022

Is your feature request related to a problem? Please describe

This issue is being used to track and increase transparency around the breaking changes planned for the 2.0 release. The goal is to help the community get a preview of the breaking changes ahead of time so that migration details can be accounted for. Feedback on the process is welcomed.

Describe the solution you'd like

Each repo who plans to release breaking changes in 2.0 needs to link to this issue. This issue will be posted on the public roadmap for the community to see and provide feedback on. Contributors will do their best to highlight breaking changes early on in the process. Community members are encouraged to add feedback to the proposed breaking changes to improve the product offering.

Describe alternatives you've considered

We will be testing this process out and will learn as we go.

Additional context

No response

@brijos brijos added enhancement New Enhancement untriaged Issues that have not yet been triaged labels Mar 18, 2022
@saratvemulapalli
Copy link
Member

Here is a meta issue for breaking changes in OpenSearch (core).
opensearch-project/OpenSearch#2480

@zelinh zelinh removed the untriaged Issues that have not yet been triaged label Mar 22, 2022
@cliu123
Copy link
Member

cliu123 commented Apr 18, 2022

Security plugin breaking changes(PR):
Security plugin will drop the rolling upgrade support ODFE -> OpenSearch 1.2.0, but will still support the upgrade patch ODFE 1.13 -> OpenSearch 1.x -> OpenSearch 2.0.0

@dblock dblock added the campaign Parent issues of OpenSearch release campaigns. label Apr 18, 2022
@seanneumann
Copy link
Contributor

seanneumann commented May 2, 2022

Dashboards issue tracking breaking changes for plugins... [2.0] Dashboards Plugin Errors #1206

Release note also cover breaking items for Dashboards

@martin-gaievski
Copy link
Member

no breaking changes for k-NN plugin

@jackiehanyang
Copy link
Contributor

jackiehanyang commented May 3, 2022

ml-commons and PPL integration has a breaking change.

  • A Kmeans command like this works in 1.3 but doesn't work in 2.0 { "query": "source=xxx | fields xxx | kmeans 2"}.
  • Vice versa, a Kmeans command like this works in 2.0 but doesn't work in 1.3 { "query": "source=xxx | fields xxx | kmeans centroids=2"}

Please see more details in Support more orderless parameters for KEMANS and AD commands

@vmmusings
Copy link
Member

sql, observability and reporting plugins have no breaking changes planned for this release.

@ankitkala
Copy link
Member

No breaking change for cross-cluster-replication

@bbarani
Copy link
Member

bbarani commented Jun 13, 2022

Closing this issue as we have released OpenSearch 2.0 version. Feel free to re-open if needed.

@bbarani bbarani closed this as completed Jun 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
campaign Parent issues of OpenSearch release campaigns. enhancement New Enhancement
Projects
None yet
Development

No branches or pull requests