From 9932f2e70af53045ae7fde9e99c38a1e66bf5596 Mon Sep 17 00:00:00 2001
From: 317brian <53799971+317brian@users.noreply.github.com>
Date: Mon, 7 Oct 2024 19:25:55 -0700
Subject: [PATCH] docs: concurrent append and replace is gA (#17269)

---
 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.