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.

Sign up for GitHub

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

Update to Breaking changes file #3550

Merged
merged 2 commits into from
Mar 23, 2023
Merged

Update to Breaking changes file #3550

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
45cdc8d
fixtobreaking2
hdhalter Mar 23, 2023
cd4b68a
fixpassivevoice
hdhalter Mar 23, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 2 additions & 5 deletions breaking-changes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,17 +12,14 @@ permalink: /breaking-changes/

The `type` parameter has been removed from all OpenSearch API endpoints. Instead, indexes can be categorized by document type. For more details, see issue [#1940](https://github.com/opensearch-project/opensearch/issues/1940).

### Deprecate outdated nomenclature
### Deprecate non-inclusive terms

In order for OpenSearch to include more inclusive naming conventions, we've replaced the following terms in our code with more inclusive terms:
Non-inclusive terms are deprecated in version 2.x and will be permanently removed in OpenSearch 3.0. We are using the following replacements:

- "Whitelist" is now "Allow list"
- "Blacklist" is now "Deny list"
- "Master" is now "Cluster Manager"

If you are using any outdated terms in the context of the security APIs or for node management, your calls and automation will continue to work in all 2.x releases. However, support for the outdated terms will be removed in 3.0 -- which will be a breaking change -- so plan accordingly.
{: .warning}

### Add OpenSearch Notifications plugins

In OpenSearch 2.0, the Alerting plugin is now integrated with new plugins for Notifications. If you want to continue to use the notification action in the Alerting plugin, install the new backend plugins `notifications-core` and `notifications`. If you want to manage notifications in OpenSearch Dashboards, use the new `notificationsDashboards` plugin. For more information, see [Questions about destinations]({{site.url}}{{site.baseurl}}/monitoring-plugins/alerting/monitors#questions-about-destinations) on the Monitors page.
Expand Down