docs: Update tutorials to not use bin/post-index-task

docs/ingestion/native-batch.md

@@ -46,7 +46,7 @@ For related information on batch indexing, see:
 To run either kind of JSON-based batch indexing task, you can:
 
 - Use the **Load Data** UI in the web console to define and submit an ingestion spec.
-- Define an ingestion spec in JSON based upon the [examples](#parallel-indexing-example) and reference topics for batch indexing. Then POST the ingestion spec to the [Tasks API endpoint](../api-reference/tasks-api.md), `/druid/indexer/v1/task`, the Overlord service. Alternatively, you can use the indexing script included with Druid at `bin/post-index-task`.
+- Define an ingestion spec in JSON based upon the [examples](#parallel-indexing-example) and reference topics for batch indexing. Then POST the ingestion spec to the [Tasks API endpoint](../api-reference/tasks-api.md), `/druid/indexer/v1/task`, the Overlord service.
 
 ## Parallel task indexing
 

docs/tutorials/tutorial-batch.md

@@ -31,7 +31,7 @@ specs by hand or using the _data loader_ built into the web console.
 
 For production environments, it's likely that you'll want to automate data ingestion. This tutorial starts by showing
 you how to submit an ingestion spec directly in the web console, and then introduces ways to ingest batch data that
-lend themselves to automation—from the command line and from a script. 
+lend themselves to automation—from the command line. 
 
 ## Loading data with a spec (via console)
 
@@ -116,52 +116,24 @@ This brings up the spec submission dialog where you can paste the spec above.
 Once the spec is submitted, wait a few moments for the data to load, after which you can query it.
 
 
-## Loading data with a spec (via command line)
+## Loading data from the command line
 
-For convenience, the Druid package includes a batch ingestion helper script at `bin/post-index-task`.
-
-This script will POST an ingestion task to the Druid Overlord and poll Druid until the data is available for querying.
+To load data from the command line, you need to POST an ingestion spec to the Druid Overlord using its task API.
 
 Run the following command from Druid package root:
 
 ```bash
-bin/post-index-task --file quickstart/tutorial/wikipedia-index.json --url http://localhost:8081
-```
-
-You should see output like the following:
-
-```bash
-Beginning indexing data for wikipedia
-Task started: index_wikipedia_2018-07-27T06:37:44.323Z
-Task log:     http://localhost:8081/druid/indexer/v1/task/index_wikipedia_2018-07-27T06:37:44.323Z/log
-Task status:  http://localhost:8081/druid/indexer/v1/task/index_wikipedia_2018-07-27T06:37:44.323Z/status
-Task index_wikipedia_2018-07-27T06:37:44.323Z still running...
-Task index_wikipedia_2018-07-27T06:37:44.323Z still running...
-Task finished with status: SUCCESS
-Completed indexing data for wikipedia. Now loading indexed data onto the cluster...
-wikipedia loading complete! You may now query your data
-```
-
-Once the spec is submitted, you can follow the same instructions as above to wait for the data to load and then query it.
-
-
-## Loading data without the script
-
-Let's briefly discuss how we would've submitted the ingestion task without using the script. You do not need to run these commands.
-
-To submit the task, POST it to Druid in a new terminal window from the `apache-druid-{{DRUIDVERSION}}` directory:
-
-```bash
-curl -X 'POST' -H 'Content-Type:application/json' -d @quickstart/tutorial/wikipedia-index.json http://localhost:8081/druid/indexer/v1/task
+curl -X POST http://localhost:8081/druid/indexer/v1/task \
+  -H "Content-Type: application/json" \
+  -d @quickstart/tutorial/wikipedia-index.json
 ```
-
-Which will print the ID of the task if the submission was successful:
+If the submission was successful, Druid will print a task ID similar to the following:
 
 ```bash
-{"task":"index_wikipedia_2018-06-09T21:30:32.802Z"}
+{"task":"index_parallel_wikipedia_oiemabcp_2026-07-07T16:05:33.242Z"}
 ```
 
-You can monitor the status of this task from the console as outlined above.
+Wait a few moments for the data to load, then move on to querying it.
 
 
 ## Querying your data

docs/tutorials/tutorial-compaction.md

@@ -45,10 +45,12 @@ This tutorial uses the Wikipedia edits sample data included with the Druid distr
 To load the initial data, you use an ingestion spec that loads batch data with segment granularity of `HOUR` and creates between one and three segments per hour.
 
 You can review the ingestion spec at `quickstart/tutorial/compaction-init-index.json`.
-Submit the spec as follows to create a datasource called `compaction-tutorial`:
+Submit the spec as follows to the Druid Overlord API to create a datasource called `compaction-tutorial`:
 
 ```bash
-bin/post-index-task --file quickstart/tutorial/compaction-init-index.json --url http://localhost:8081
+curl -X POST http://localhost:8081/druid/indexer/v1/task \
+  -H "Content-Type: application/json" \
+  -d @quickstart/tutorial/compaction-init-index.json
 ```
 
 :::info
@@ -106,7 +108,9 @@ This datasource only has 39,244 rows. 39,244 is below the default limit of 5,000
 Submit the compaction task now:
 
 ```bash
-bin/post-index-task --file quickstart/tutorial/compaction-keep-granularity.json --url http://localhost:8081
+curl -X POST http://localhost:8081/druid/indexer/v1/task \
+  -H "Content-Type: application/json" \
+  -d @quickstart/tutorial/compaction-keep-granularity.json
 ```
 
 After the task finishes, refresh the [segments view](http://localhost:8888/unified-console.html#segments).
@@ -169,10 +173,12 @@ The Druid distribution includes a compaction task spec to create `DAY` granulari
 
 Note that `segmentGranularity` is set to `DAY` in this compaction task spec.
 
-Submit this task now:
+Now, submit this task:
 
 ```bash
-bin/post-index-task --file quickstart/tutorial/compaction-day-granularity.json --url http://localhost:8081
+curl -X POST http://localhost:8081/druid/indexer/v1/task \
+  -H "Content-Type: application/json" \
+  -d @quickstart/tutorial/compaction-day-granularity.json
 ```
 
 It takes some time before the Coordinator marks the old input segments as unused, so you may see an intermediate state with 25 total segments. Eventually, only one DAY granularity segment remains:

docs/tutorials/tutorial-delete-data.md

@@ -34,10 +34,12 @@ This tutorial requires the following:
 
 In this tutorial, we will use the Wikipedia edits data, with an indexing spec that creates hourly segments. This spec is located at `quickstart/tutorial/deletion-index.json`, and it creates a datasource called `deletion-tutorial`.
 
-Let's load this initial data:
+Let's load our initial data by calling Druid Overlord:
 
 ```bash
-bin/post-index-task --file quickstart/tutorial/deletion-index.json --url http://localhost:8081
+curl -X POST http://localhost:8081/druid/indexer/v1/task \
+  -H "Content-Type: application/json" \
+  -d @quickstart/tutorial/deletion-index.json
 ```
 
 When the load finishes, open [http://localhost:8888/unified-console.md#datasources](http://localhost:8888/unified-console.html#datasources) in a browser.

docs/tutorials/tutorial-ingestion-spec.md

@@ -580,13 +580,15 @@ We've finished defining the ingestion spec, it should now look like the followin
 
 ## Submit the task and query the data
 
-From the `apache-druid-{{DRUIDVERSION}}` package root, run the following command:
+From the `apache-druid-{{DRUIDVERSION}}` package root, run the following command to create a datasource called `ingestion tutorial`:
 
 ```bash
-bin/post-index-task --file quickstart/ingestion-tutorial-index.json --url http://localhost:8081
+curl -X POST http://localhost:8081/druid/indexer/v1/task \
+  -H "Content-Type: application/json" \
+  -d @quickstart/ingestion-tutorial-index.json
 ```
 
-After the script completes, we will query the data.
+After the ingestion completes, we will query the data.
 
 In the web console, open a new tab in the **Query** view. Run the following query to view the ingested data:
 
@@ -602,4 +604,4 @@ Returns the following:
 | `2018-01-01T01:02:00.000Z` |  `9000` | `18.1` | `2` | `2.2.2.2` | `7000` | `90` | `6` | `1.1.1.1` | `5000` |
 | `2018-01-01T01:03:00.000Z` | `6000` |  `4.3` | `1` | `2.2.2.2` | `7000` | `60` | `6` | `1.1.1.1` | `5000` |
 | `2018-01-01T02:33:00.000Z` | `30000` | `56.9` | `2` | `8.8.8.8` | `5000` | `300` | `17` | `7.7.7.7` | `4000` |
-| `2018-01-01T02:35:00.000Z` | `30000` | `46.3` | `1` | `8.8.8.8` | `5000` | `300` | `17` | `7.7.7.7` | `4000` |
+| `2018-01-01T02:35:00.000Z` | `30000` | `46.3` | `1` | `8.8.8.8` | `5000` | `300` | `17` | `7.7.7.7` | `4000` |

docs/tutorials/tutorial-retention.md

@@ -35,10 +35,12 @@ It will also be helpful to have finished [Load a file](../tutorials/tutorial-bat
 
 For this tutorial, we'll be using the Wikipedia edits sample data, with an ingestion task spec that will create a separate segment for each hour in the input data.
 
-The ingestion spec can be found at `quickstart/tutorial/retention-index.json`. Let's submit that spec, which will create a datasource called `retention-tutorial`:
+The ingestion spec can be found at `quickstart/tutorial/retention-index.json`. Let's submit that spec by calling Druid Overlord, which will create a datasource called `retention-tutorial`:
 
 ```bash
-bin/post-index-task --file quickstart/tutorial/retention-index.json --url http://localhost:8081
+curl -X POST http://localhost:8081/druid/indexer/v1/task \
+  -H "Content-Type: application/json" \
+  -d @quickstart/tutorial/retention-index.json
 ```
 
 After the ingestion completes, go to [http://localhost:8888/unified-console.html#datasources](http://localhost:8888/unified-console.html#datasources) in a browser to access the web console's datasource view.