gianm commented on code in PR #12350:
URL: https://github.com/apache/druid/pull/12350#discussion_r873071140
##########
docs/ingestion/native-batch.md:
##########
@@ -387,19 +400,44 @@ them to create the final segments. Finally, they push the
final segments to the
> the task may fail if the input changes in between the two passes.
#### Multi-dimension range partitioning
-> Multiple dimension (multi-dimension) range partitioning is an experimental
feature. Multi-dimension range partitioning is currently not supported in the
sequential mode of the Parallel task.
-When you use multi-dimension partitioning for your data, Druid is able to
distribute segment sizes more evenly than with single dimension partitioning.
+> Multiple dimension (multi-dimension) range partitioning is an experimental
feature.
+> Multi-dimension range partitioning is currently not supported in the
sequential mode of the
+> Parallel task.
-For segment pruning to be effective and translate into better query
performance, you must include the first of your `partitionDimensions` in the
`WHERE` clause at query time. For example, given the following
`partitionDimensions`:
-```
- "partitionsSpec": {
- "type": "range",
- "partitionDimensions":["coutryName","cityName"],
- "targetRowsPerSegment" : 5000
+When you use multi-dimension range partitioning for your data, Druid is able
to distribute segment
+sizes more evenly than with single dimension partitioning.
+
+Range partitioning has several benefits:
Review Comment:
I made this change.
--
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]
