mirror of https://github.com/apache/druid.git
a8b916576d
* Allow for appending tasks to co-exist with each other. Add a config parameter for appending tasks to allow them to use a SHARED lock. This will allow multiple appending tasks to add segments to the same datasource at the same time. This config should actually be the default, but it is added as a config to enable a smooth transition/validation in production settings before forcing it as the default behavior going forward. This change leverages the TaskLockType.SHARED that existed previously, this used to carry the semantics of a READ lock, which was "escalated" when the task wanted to actually persist the segment. As of many moons before this diff, the SHARED lock had stopped being used but was still piped into the code. It turns out that with a few tweaks, it can be adjusted to be a shared lock for append tasks to allow them all to write to the same datasource, so that is what this does. * Can only reuse the shared lock if using the same groupId * Need to serialize out the task lock type * Adjust Unit tests to expect new field in JSON |
||
|---|---|---|
| .. | ||
| src | ||
| pom.xml | ||