Apache Druid

from documentation:
```When the segment lock is used, a task locks individual segments instead of the entire time chunk. As a result, two or more tasks can create segments for the same time chunk of the same data source simultaneously if they are reading different segments. For example, a Kafka indexing task and a compaction task can always write segments into the same time chunk of the same data source simultaneously. The reason for this is because a Kafka indexing task always appends new segments, while a compaction task always overwrites existing segments. The segments created with the segment locking have the same major version and a higher minor version.

The segment locking is still experimental. It could have unknown bugs which potentially lead to incorrect query results.```
<https://druid.apache.org/docs/latest/ingestion/tasks.html#locking>

I think there are still issues with it.  Usual approach is to use a combination of rejecting data that's too late, and not compacting data for some period (eg, a 1 day offset).