ektravel commented on code in PR #14560: URL: https://github.com/apache/druid/pull/14560#discussion_r1261644806
########## docs/querying/segmentmetadataquery.md: ########## @@ -62,7 +62,8 @@ There are several main parts to a segment metadata query: |merge|Merge all individual segment metadata results into a single result|no| |context|See [Context](../querying/query-context.md)|no| |analysisTypes|A list of Strings specifying what column properties (e.g. cardinality, size) should be calculated and returned in the result. Defaults to ["cardinality", "interval", "minmax"], but can be overridden with using the [segment metadata query config](../configuration/index.md#segmentmetadata-query-config). See section [analysisTypes](#analysistypes) for more details.|no| -|lenientAggregatorMerge|If true, and if the "aggregators" analysisType is enabled, aggregators will be merged leniently. See below for details.|no| +|aggregatorMergeStrategy| The strategy used to merge aggregators across segments. If true, and if the "aggregators" analysisType is enabled, it defaults to "strict". Possible values include "strict", "lenient" and "latest". See [below](#aggregatormergestrategy) for details.|no| Review Comment: ```suggestion |aggregatorMergeStrategy| The strategy Druid uses to merge aggregators across segments. If true and if the `aggregators` analysis type is enabled, `aggregatorMergeStrategy` defaults to `strict`. Possible values include `strict`, `lenient`, and `latest`. See [aggregatorMergeStrategy](#aggregatormergestrategy) for details.|no| ``` -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
