(druid) branch master updated: Docs: List limitations of concurrent append and replace (#17852)

[ka...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

karan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/druid.git


The following commit(s) were added to refs/heads/master by this push:
     new d8c6c8e4d37 Docs: List limitations of concurrent append and replace (#17852)
d8c6c8e4d37 is described below

commit d8c6c8e4d376a113ef8386fff3ab5dc10c34849b
Author: Kashif Faraz <ka...@gmail.com>
AuthorDate: Tue Apr 1 11:42:30 2025 +0530

    Docs: List limitations of concurrent append and replace (#17852)
---
 docs/ingestion/concurrent-append-replace.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/ingestion/concurrent-append-replace.md b/docs/ingestion/concurrent-append-replace.md
index 607fbedfc48..d8b7bdbddcb 100644
--- a/docs/ingestion/concurrent-append-replace.md
+++ b/docs/ingestion/concurrent-append-replace.md
@@ -143,3 +143,10 @@ Set  `taskLockType` to `REPLACE` if you're replacing data. For example, if you u
 - dynamic partitioning with append to existing set to `false`
 
 </details>
+
+## Known limitations
+
+Do not use concurrent append and replace on a datasource if any one of the following is true:
+
+- The datasource has mixed granularity of data in any interval. For example, if an interval has both DAY and WEEK granularity data, using concurrent append and replace may result in data loss or duplication.
+- The datasource has a compaction config which compacts data into more granular chunks. For example, a datasource that has MONTH data ingested into it and is configured to compact it into DAY granularity might suffer data losses or duplication.


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org