wu-sheng commented on a change in pull request #7634:
URL: https://github.com/apache/skywalking/pull/7634#discussion_r702418051
##########
File path: docs/en/setup/backend/backend-storage.md
##########
@@ -34,23 +34,18 @@ storage:
## OpenSearch
-OpenSearch storage shares the same configurations as ElasticSearch 7.
-In order to activate ElasticSearch 7 as storage, set storage provider to
**elasticsearch7**.
-Please download the `apache-skywalking-bin-es7.tar.gz` if you want to use
OpenSearch as storage.
+OpenSearch storage shares the same configurations as ElasticSearch.
+In order to activate OpenSearch as storage, set storage provider to
**elasticsearch**.
## ElasticSearch
**NOTE:** Elastic announced through their blog that Elasticsearch will be
moving over to a Server Side Public
License (SSPL), which is incompatible with Apache License 2.0. This license
change is effective from Elasticsearch
version 7.11. So please choose the suitable ElasticSearch version according to
your usage.
-- In order to activate ElasticSearch 6 as storage, set storage provider to
**elasticsearch**
-- In order to activate ElasticSearch 7 as storage, set storage provider to
**elasticsearch7**
-
-**Required ElasticSearch 6.3.2 or higher. HTTP RestHighLevelClient is used to
connect server.**
-
-- For ElasticSearch 6.3.2 ~ 7.0.0 (excluded), please download
`apache-skywalking-bin.tar.gz`.
-- For ElasticSearch 7.0.0 ~ 8.0.0 (excluded), please download
`apache-skywalking-bin-es7.tar.gz`.
+Since 8.8.0, SkyWalking rebuilds the ElasticSearch client on top of
ElasticSearch REST API and automatically picks up
+correct request formats according to the server side version, hence you don't
need to download different binaries
+and don't need to configure different storage selector for different
ElasticSearch server side version anymore.
Review comment:
I think we still need to indicate the supported-versions range.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
