QiuMM commented on a change in pull request #6780: Add support 
maxRowsPerSegment for auto compaction
URL: https://github.com/apache/incubator-druid/pull/6780#discussion_r245498840
 
 

 ##########
 File path: docs/content/ingestion/compaction.md
 ##########
 @@ -47,7 +47,8 @@ Compaction tasks merge all segments of the given interval. 
The syntax is:
 |`id`|Task id|No|
 |`dataSource`|DataSource name to be compacted|Yes|
 |`interval`|Interval of segments to be compacted|Yes|
-|`dimensions`|Custom dimensionsSpec. compaction task will use this 
dimensionsSpec if exist instead of generating one. See below for more 
details.|No|
+|`dimensionsSpec`|Custom dimensionsSpec. Compaction task will use this 
dimensionsSpec if exist instead of generating one. See below for more 
details.|No|
+|`metricsSpec`|Custom metricsSpec. Compaction task will use this metricsSpec 
if specified rather than generating one.|No|
 |`segmentGranularity`|If this is set, compactionTask will change the segment 
granularity for the given interval. See [segmentGranularity of Uniform 
Granularity Spec](./ingestion-spec.html#uniform-granularity-spec) for more 
details. See the below table for the behavior.|No|
 |`keepSegmentGranularity`|Deprecated. Please use `segmentGranularity` instead. 
See the below table for its behavior.|No|
 |`targetCompactionSizeBytes`|Target segment size after comapction. Cannot be 
used with `targetPartitionSize`, `maxTotalRows`, and `numShards` in 
tuningConfig.|No|
 
 Review comment:
   Still is `targetPartitionSize`?  And after look into the code, it seems 
there is no `maxRowsPerSegment` for compaction tuningConfig.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to