jon-wei commented on a change in pull request #11189:
URL: https://github.com/apache/druid/pull/11189#discussion_r627847812
##########
File path: docs/ingestion/tasks.md
##########
@@ -347,9 +347,10 @@ The task context is used for various individual task
configuration. The followin
|property|default|description|
|--------|-------|-----------|
-|taskLockTimeout|300000|task lock timeout in millisecond. For more details,
see [Locking](#locking).|
-|forceTimeChunkLock|true|_Setting this to false is still experimental_<br/>
Force to always use time chunk lock. If not set, each task automatically
chooses a lock type to use. If this set, it will overwrite the
`druid.indexer.tasklock.forceTimeChunkLock` [configuration for the
overlord](../configuration/index.md#overlord-operations). See
[Locking](#locking) for more details.|
-|priority|Different based on task types. See [Priority](#priority).|Task
priority|
+|`taskLockTimeout`|300000|task lock timeout in millisecond. For more details,
see [Locking](#locking).|
+|`forceTimeChunkLock`|true|_Setting this to false is still experimental_<br/>
Force to always use time chunk lock. If not set, each task automatically
chooses a lock type to use. If this set, it will overwrite the
`druid.indexer.tasklock.forceTimeChunkLock` [configuration for the
overlord](../configuration/index.md#overlord-operations). See
[Locking](#locking) for more details.|
+|`priority`|Different based on task types. See [Priority](#priority).|Task
priority|
+|`useLineageBasedSegmentAllocation`|false|Enable the new lineage-based segment
allocation protocol for the native Parallel task with dynamic partitioning.
This option should be off during the replacing rolling upgrade to Druid 0.22 or
higher. Once the upgrade is done, it must be set to true.|
Review comment:
Suggest also adding a note that this applies if upgrading from a
pre-0.22.0 version
--
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]
