[GitHub] [skywalking] wu-sheng commented on a change in pull request #6499: merge telemetry index

[GitBox <gi...@apache.org>]

wu-sheng commented on a change in pull request #6499:
URL: https://github.com/apache/skywalking/pull/6499#discussion_r588836706



##########
File path: docs/en/setup/backend/backend-storage.md
##########
@@ -72,6 +72,8 @@ storage:
     oapAnalyzer: ${SW_STORAGE_ES_OAP_ANALYZER:"{\"analyzer\":{\"oap_analyzer\":{\"type\":\"stop\"}}}"} # the oap analyzer.
     oapLogAnalyzer: ${SW_STORAGE_ES_OAP_LOG_ANALYZER:"{\"analyzer\":{\"oap_log_analyzer\":{\"type\":\"standard\"}}}"} # the oap log analyzer. It could be customized by the ES analyzer configuration to support more language log formats, such as Chinese log, Japanese log and etc.
     advanced: ${SW_STORAGE_ES_ADVANCED:""}
+    storageMode: ${SW_STORAGE_ES_MODE:FUNCTIONAL_AGGREGATION}#There are 2 mode for indices storage, which are FUNCTIONAL_AGGREGATION and NO_AGGREGATION. The Storage behavior using NO_AGGREGATION is same with the storage behavior before 8.5.0 version. And, the Storage behavior using FUNCTIONAL_AGGREGATION means the telemetry data, that generated by OAL or MAL, would be partitioned by the functions of the OAL or MAL.

Review comment:
       I think we could do permanent change rather than 2 modes. This new one is always better and recommended. Right?




----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org