This is an automated email from the ASF dual-hosted git repository.
kfaraz pushed a commit to branch 31.0.0
in repository https://gitbox.apache.org/repos/asf/druid.git
The following commit(s) were added to refs/heads/31.0.0 by this push:
new b30eab36b94 docs: concurrent append and replace is gA (#17269) (#17273)
b30eab36b94 is described below
commit b30eab36b94fba437491999ab52af14f96d5df5d
Author: Kashif Faraz <[email protected]>
AuthorDate: Tue Oct 8 09:37:43 2024 +0530
docs: concurrent append and replace is gA (#17269) (#17273)
Co-authored-by: 317brian <[email protected]>
---
docs/ingestion/concurrent-append-replace.md | 4 ----
1 file changed, 4 deletions(-)
diff --git a/docs/ingestion/concurrent-append-replace.md
b/docs/ingestion/concurrent-append-replace.md
index 5e9286de5e6..0ac5b881564 100644
--- a/docs/ingestion/concurrent-append-replace.md
+++ b/docs/ingestion/concurrent-append-replace.md
@@ -22,10 +22,6 @@ title: Concurrent append and replace
~ under the License.
-->
-:::info
-Concurrent append and replace is an [experimental
feature](../development/experimental.md) available for JSON-based batch,
streaming, and SQL-based ingestion.
-:::
-
Concurrent append and replace safely replaces the existing data in an interval
of a datasource while new data is being appended to that interval. One of the
most common applications of this feature is appending new data (such as with
streaming ingestion) to an interval while compaction of that interval is
already in progress. Druid segments the data ingested during this time
dynamically. The subsequent compaction run segments the data into the
granularity you specified.
To set up concurrent append and replace, use the context flag
`useConcurrentLocks`. Druid will then determine the correct lock type for you,
either append or replace. Although you can set the type of lock manually, we
don't recommend it.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
