-
Notifications
You must be signed in to change notification settings - Fork 142
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
[Release 3.0] Planned Breaking Changes for 3.0 in Plugin #3248
Comments
IMO, OpenSearch DSL format support could be consided deperated in 3.0. The reasons are
|
SQL Plugin Breaking Change TrackerAs part of the OpenSearch 3.0 release plan, we intend to introduce breaking changes. To align with the release timeline, we have defined the following review and decision process: 1. Breaking Change Proposal CollectionWe are collecting breaking change proposals. Please add your comments to this thread. 2. Review and FinalizationA meeting will be scheduled during the last week of January 2025 to review the proposed changes with the maintainers. Criteria for Breaking Change CandidatesFeatures that meet any of the following criteria are considered strong candidates for breaking changes:
|
Settings
PPL
ConnectorThe Prometheus connector and Spark connector are considered experimental features, as they have limited adoption and do not align with our long-term goals. We could consider deprecating them. |
In 3.0, we should deprecate the setting to move to PIT from scroll. We can make PIT the default one. |
Breaking behavior in 3.0+
Reference |
[Release 3.0] Planned Breaking Changes for 3.0 in Plugin
As mentioned in this META Issue, we want to track and increase transparency around the breaking changes planned for the 3.0 release across participating plugins.
Please kindly document all planned breaking changes related to your plugin for 3.0 here, by sharing detailed information about the changes, expected impact, and any guidance for users or other teams to adapt to the changes.
If needed, please also prepare PRs on documentation-website changes as part of the 3.0 release process.
Overall, this would help us deliver a smooth and seamless upgrade experience.
Thanks.
Breaking behavior in 3.0+
The text was updated successfully, but these errors were encountered: