abhishekagarwal87 commented on a change in pull request #10243:
URL: https://github.com/apache/druid/pull/10243#discussion_r470734118
##########
File path: docs/ingestion/native-batch.md
##########
@@ -232,7 +232,8 @@ The size-based split hint spec is respected by all
splittable input sources exce
|property|description|default|required?|
|--------|-----------|-------|---------|
|type|This should always be `maxSize`.|none|yes|
-|maxSplitSize|Maximum number of bytes of input files to process in a single
task. If a single file is larger than this number, it will be processed by
itself in a single task (Files are never split across tasks yet).|500MB|no|
+|maxSplitSize|Maximum number of bytes of input files to process in a single
task. If a single file is larger than this number, it will be processed by
itself in a single task (Files are never split across tasks yet).
[Human-readable format](../configuration/human-readable-byte.md) is
supported.|500MiB|no|
+|maxNumFiles|Maximum number of input files to process in a single task. This
limit is to avoid task failures when the ingestion spec is too long. There are
two known limits on the max size of serialized ingestion spec, i.e., the max
ZNode size in ZooKeeper (`jute.maxbuffer`) and the max packet size in MySQL
(`max_allowed_packet`). These can make ingestion tasks fail if the serialized
ingestion spec size hits one of them.|5000|no|
Review comment:
```suggestion
|maxNumFiles|Maximum number of input files to process in a single task. This
limit is to avoid task failures when the ingestion spec is too long. There are
two known limits on the max size of serialized ingestion spec, i.e., the max
ZNode size in ZooKeeper (`jute.maxbuffer`) and the max packet size in MySQL
(`max_allowed_packet`). These can make ingestion tasks fail if the serialized
ingestion spec size hits one of them.|1000|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.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
