Skip to content

update compatibility matrix and remove setting [issue 517] #558

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

Merged
alicejw1 merged 8 commits into from
May 23, 2022
Merged

update compatibility matrix and remove setting [issue 517] #558

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
fff42db
remove instances of setting that is no longer available in OS2.0
May 5, 2022
31decfa
add note to legacy clients matrix
May 5, 2022
776c6fe
update note for 2.0 incompatible with legacy clients
May 5, 2022
da027fb
for issue 517 override setting not supported for legacy clients in Op…
May 16, 2022
7dbe65f
for clarity about setting deprecated in 1.x and removed in 2.0.
May 16, 2022
997bd48
for requester's PR review and updates for accuracy
May 18, 2022
bd5e27a
for small fix to move note syntax into commented-out section
May 18, 2022
90a5a61
for editor's feedback updates
May 23, 2022
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
4 changes: 2 additions & 2 deletions _clients/agents-and-ingestion-tools/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,13 +26,13 @@ PUT _cluster/settings
}
}
```

<!-- This setting is deprecated in 1.0 and removed from 2.0
[Just like any other setting]({{site.url}}{{site.baseurl}}/opensearch/configuration/), the alternative is to add the following line to `opensearch.yml` on each node and then restart the node:

```yml
compatibility.override_main_response_version: true
```

-->
Logstash OSS 8.0 introduces a breaking change where all plugins run in ECS compatibility mode by default. If you use a compatible [OSS client](#compatibility-matrices) you must override the default value to maintain legacy behavior:

```yml
Expand Down
4 changes: 4 additions & 0 deletions _clients/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,10 @@ For example, a 1.0.0 client works with an OpenSearch 1.1.0 cluster, but might no

Most clients that work with Elasticsearch OSS 7.10.2 *should* work with OpenSearch, but the latest versions of those clients might include license or version checks that artificially break compatibility. This page includes recommendations around which versions of those clients to use for best compatibility with OpenSearch.

{: .note}
OpenSearch 2.0.0 no longer supports compatibility with legacy clients. Due to breaking changes with REST APIs, clients using older OpenSearch 1.x versions can't connect with OpenSearch 2.0.
Comment thread
alicejw1 marked this conversation as resolved.
Outdated


Client | Recommended version
:--- | :---
[Java low-level REST client](https://search.maven.org/artifact/org.elasticsearch.client/elasticsearch-rest-client/7.13.4/jar) | 7.13.4
Expand Down
1 change: 0 additions & 1 deletion _opensearch/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,6 @@ You don't mark settings in `opensearch.yml` as persistent or transient, and sett
```yml
cluster.name: my-application
action.auto_create_index: true
compatibility.override_main_response_version: true
```

The demo configuration includes a number of settings for the security plugin that you should modify before using OpenSearch for a production workload. To learn more, see [Security]({{site.url}}{{site.baseurl}}/security-plugin/).