You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by te...@apache.org on 2023/12/06 21:13:13 UTC

(druid) branch master updated: Re-arranging sections for append and replace docs. (#15497)

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

techdocsmith 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 fea53c7084b Re-arranging sections for append and replace docs. (#15497)
fea53c7084b is described below

commit fea53c7084ba07aefb7486c4935f4eac94783065
Author: Benjamin Hopp <be...@imply.io>
AuthorDate: Wed Dec 6 14:13:05 2023 -0700

    Re-arranging sections for append and replace docs. (#15497)
---
 docs/data-management/automatic-compaction.md | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/docs/data-management/automatic-compaction.md b/docs/data-management/automatic-compaction.md
index 4de4f1f3763..4a58537791a 100644
--- a/docs/data-management/automatic-compaction.md
+++ b/docs/data-management/automatic-compaction.md
@@ -233,6 +233,10 @@ When using concurrent append and replace, keep the following in mind:
 
 ### Configure concurrent append and replace
 
+##### Update the compaction settings with the UI
+
+In the **Compaction config** for a datasource, set  **Allow concurrent compactions (experimental)** to **True**.
+
 ##### Update the compaction settings with the API
  
  Prepare your datasource for concurrent append and replace by setting its task lock type to `REPLACE`.
@@ -249,9 +253,6 @@ curl --location --request POST 'http://localhost:8081/druid/coordinator/v1/confi
 }'
 ```
 
-##### Update the compaction settings with the UI
-
-In the **Compaction config** for a datasource, set  **Allow concurrent compactions (experimental)** to **True**.
 
 #### Add a task lock type to your ingestion job
 
@@ -262,6 +263,13 @@ Next, you need to configure the task lock type for your ingestion job:
  
 You can provide the context parameter through the API like any other parameter for ingestion job or through the UI.
 
+##### Add a task lock using the Druid console
+
+As part of the  **Load data** wizard for classic batch (JSON-based ingestion) and streaming ingestion, you can configure the task lock type for the ingestion during the **Publish** step:
+
+- If you set **Append to existing** to **True**, you can then set **Allow concurrent append tasks (experimental)** to **True**.
+- If you set **Append to existing** to **False**, you can then set **Allow concurrent replace tasks (experimental)** to **True**.
+
 ##### Add the task lock type through the API
 
 Add the following JSON snippet to your supervisor or ingestion spec if you're using the API:
@@ -295,14 +303,6 @@ Set  `taskLockType` to `REPLACE` if you're replacing data. For example, if you u
 - dynamic partitioning with append to existing set to `false`
 
 
-##### Add a task lock using the Druid console
-
-As part of the  **Load data** wizard for classic batch (JSON-based ingestion) and streaming ingestion, you can configure the task lock type for the ingestion during the **Publish** step:
-
-- If you set **Append to existing** to **True**, you can then set **Allow concurrent append tasks (experimental)** to **True**.
-- If you set **Append to existing** to **False**, you can then set **Allow concurrent replace tasks (experimental)** to **True**.
-
-
 ## Learn more
 
 See the following topics for more information:


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