Kashif Faraz feeb4f0fb0 Allocate pending segments at latest committed version (#15459) ... The segment allocation algorithm reuses an already allocated pending segment if the new allocation request is made for the same parameters: datasource sequence name same interval same value of skipSegmentLineageCheck (false for batch append, true for streaming append) same previous segment id (used only when skipSegmentLineageCheck = false) The above parameters can thus uniquely identify a pending segment (enforced by the UNIQUE constraint on the sequence_name_prev_id_sha1 column in druid_pendingSegments metadata table). This reuse is done in order to allow replica tasks (in case of streaming ingestion) to use the same set of segment IDs. allow re-run of a failed batch task to use the same segment ID and prevent unnecessary allocations		2023-12-14 16:18:39 +05:30
..
src	Allocate pending segments at latest committed version (#15459)	2023-12-14 16:18:39 +05:30
pom.xml	Prepare master for Druid 29 (#15121)	2023-10-11 10:33:45 +05:30