2018-12-13 14:47:20 -05:00
---
layout: doc_page
title: "Tutorial: Deleting data"
---
2018-11-13 12:38:37 -05:00
<!--
~ Licensed to the Apache Software Foundation (ASF) under one
~ or more contributor license agreements. See the NOTICE file
~ distributed with this work for additional information
~ regarding copyright ownership. The ASF licenses this file
~ to you under the Apache License, Version 2.0 (the
~ "License"); you may not use this file except in compliance
~ with the License. You may obtain a copy of the License at
~
~ http://www.apache.org/licenses/LICENSE-2.0
~
~ Unless required by applicable law or agreed to in writing,
~ software distributed under the License is distributed on an
~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
~ KIND, either express or implied. See the License for the
~ specific language governing permissions and limitations
~ under the License.
-->
2018-08-09 16:37:52 -04:00
# Tutorial: Deleting data
This tutorial demonstrates how to delete existing data.
2019-04-19 18:52:26 -04:00
For this tutorial, we'll assume you've already downloaded Apache Druid (incubating) as described in
2018-08-09 16:37:52 -04:00
the [single-machine quickstart ](index.html ) and have it running on your local machine.
## Load initial data
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:
2018-08-13 14:11:32 -04:00
```bash
2019-05-16 14:13:48 -04:00
bin/post-index-task --file quickstart/tutorial/deletion-index.json --url http://localhost:8081
2018-08-09 16:37:52 -04:00
```
2019-02-27 22:50:31 -05:00
When the load finishes, open [http://localhost:8888/unified-console.html#datasources ](http://localhost:8888/unified-console.html#datasources ) in a browser.
2018-08-09 16:37:52 -04:00
## How to permanently delete data
Permanent deletion of a Druid segment has two steps:
2019-05-15 17:40:06 -04:00
1. The segment must first be marked as "unused". This occurs when a user manually disables a segment through the Coordinator API.
2018-08-09 16:37:52 -04:00
2. After segments have been marked as "unused", a Kill Task will delete any "unused" segments from Druid's metadata store as well as deep storage.
2019-05-15 17:40:06 -04:00
Let's drop some segments now, by using the coordinator API to drop data by interval and segmentIds.
2018-08-09 16:37:52 -04:00
2019-05-15 17:40:06 -04:00
## Disable segments by interval
2018-08-09 16:37:52 -04:00
2019-05-15 17:40:06 -04:00
Let's disable segments in a specified interval. This will mark all segments in the interval as "unused", but not remove them from deep storage.
Let's disable segments in interval `2015-09-12T18:00:00.000Z/2015-09-12T20:00:00.000Z` i.e. between hour 18 and 20.
2018-08-09 16:37:52 -04:00
2019-05-15 17:40:06 -04:00
```bash
curl -X 'POST' -H 'Content-Type:application/json' -d '{ "interval" : "2015-09-12T18:00:00.000Z/2015-09-12T20:00:00.000Z" }' http://localhost:8081/druid/coordinator/v1/datasources/deletion-tutorial/markUnused
```
2019-02-27 22:50:31 -05:00
2019-05-15 17:40:06 -04:00
After that command completes, you should see that the segment for hour 18 and 19 have been disabled:
2018-08-09 16:37:52 -04:00
2019-05-15 17:40:06 -04:00
![Segments 2 ](../tutorials/img/tutorial-deletion-02.png "Segments 2" )
2018-08-09 16:37:52 -04:00
2019-05-15 17:40:06 -04:00
Note that the hour 18 and 19 segments are still present in deep storage:
2018-08-09 16:37:52 -04:00
2018-08-13 14:11:32 -04:00
```bash
2018-08-09 16:37:52 -04:00
$ ls -l1 var/druid/segments/deletion-tutorial/
2015-09-12T00:00:00.000Z_2015-09-12T01:00:00.000Z
2015-09-12T01:00:00.000Z_2015-09-12T02:00:00.000Z
2015-09-12T02:00:00.000Z_2015-09-12T03:00:00.000Z
2015-09-12T03:00:00.000Z_2015-09-12T04:00:00.000Z
2015-09-12T04:00:00.000Z_2015-09-12T05:00:00.000Z
2015-09-12T05:00:00.000Z_2015-09-12T06:00:00.000Z
2015-09-12T06:00:00.000Z_2015-09-12T07:00:00.000Z
2015-09-12T07:00:00.000Z_2015-09-12T08:00:00.000Z
2015-09-12T08:00:00.000Z_2015-09-12T09:00:00.000Z
2015-09-12T09:00:00.000Z_2015-09-12T10:00:00.000Z
2015-09-12T10:00:00.000Z_2015-09-12T11:00:00.000Z
2015-09-12T11:00:00.000Z_2015-09-12T12:00:00.000Z
2015-09-12T12:00:00.000Z_2015-09-12T13:00:00.000Z
2015-09-12T13:00:00.000Z_2015-09-12T14:00:00.000Z
2015-09-12T14:00:00.000Z_2015-09-12T15:00:00.000Z
2015-09-12T15:00:00.000Z_2015-09-12T16:00:00.000Z
2015-09-12T16:00:00.000Z_2015-09-12T17:00:00.000Z
2015-09-12T17:00:00.000Z_2015-09-12T18:00:00.000Z
2015-09-12T18:00:00.000Z_2015-09-12T19:00:00.000Z
2015-09-12T19:00:00.000Z_2015-09-12T20:00:00.000Z
2015-09-12T20:00:00.000Z_2015-09-12T21:00:00.000Z
2015-09-12T21:00:00.000Z_2015-09-12T22:00:00.000Z
2015-09-12T22:00:00.000Z_2015-09-12T23:00:00.000Z
2015-09-12T23:00:00.000Z_2015-09-13T00:00:00.000Z
```
2019-05-15 17:40:06 -04:00
## Disable segments by segment IDs
2018-08-09 16:37:52 -04:00
2019-05-15 17:40:06 -04:00
Let's disable some segments by their segmentID. This will again mark the segments as "unused", but not remove them from deep storage. You can see the full segmentID for a segment from UI as explained below.
2018-08-09 16:37:52 -04:00
2019-02-27 22:50:31 -05:00
In the [segments view ](http://localhost:8888/unified-console.html#segments ), click the arrow on the left side of one of the remaining segments to expand the segment entry:
2018-08-09 16:37:52 -04:00
![Segments ](../tutorials/img/tutorial-deletion-01.png "Segments" )
2019-02-27 22:50:31 -05:00
The top of the info box shows the full segment ID, e.g. `deletion-tutorial_2015-09-12T14:00:00.000Z_2015-09-12T15:00:00.000Z_2019-02-28T01:11:51.606Z` for the segment of hour 14.
2018-08-09 16:37:52 -04:00
2019-05-15 17:40:06 -04:00
Let's disable the hour 13 and 14 segments by sending a POST request to the Coordinator with this payload
```json
{
"segmentIds":
[
"deletion-tutorial_2015-09-12T13:00:00.000Z_2015-09-12T14:00:00.000Z_2019-05-01T17:38:46.961Z",
"deletion-tutorial_2015-09-12T14:00:00.000Z_2015-09-12T15:00:00.000Z_2019-05-01T17:38:46.961Z"
]
}
```
This payload json has been provided at `quickstart/tutorial/deletion-disable-segments.json` . Submit the POST request to Coordinator like this:
2018-08-09 16:37:52 -04:00
2018-08-13 14:11:32 -04:00
```bash
2019-05-15 17:40:06 -04:00
curl -X 'POST' -H 'Content-Type:application/json' -d @quickstart/tutorial/deletion -disable-segments.json http://localhost:8081/druid/coordinator/v1/datasources/deletion-tutorial/markUnused
2018-08-09 16:37:52 -04:00
```
2019-05-15 17:40:06 -04:00
After that command completes, you should see that the segments for hour 13 and 14 have been disabled:
2018-08-09 16:37:52 -04:00
2019-05-15 17:40:06 -04:00
![Segments 3 ](../tutorials/img/tutorial-deletion-03.png "Segments 3" )
2018-08-09 16:37:52 -04:00
2019-05-15 17:40:06 -04:00
Note that the hour 13 and 14 segments are still in deep storage:
2018-08-09 16:37:52 -04:00
2018-08-13 14:11:32 -04:00
```bash
2018-08-09 16:37:52 -04:00
$ ls -l1 var/druid/segments/deletion-tutorial/
2015-09-12T00:00:00.000Z_2015-09-12T01:00:00.000Z
2015-09-12T01:00:00.000Z_2015-09-12T02:00:00.000Z
2015-09-12T02:00:00.000Z_2015-09-12T03:00:00.000Z
2015-09-12T03:00:00.000Z_2015-09-12T04:00:00.000Z
2015-09-12T04:00:00.000Z_2015-09-12T05:00:00.000Z
2015-09-12T05:00:00.000Z_2015-09-12T06:00:00.000Z
2015-09-12T06:00:00.000Z_2015-09-12T07:00:00.000Z
2015-09-12T07:00:00.000Z_2015-09-12T08:00:00.000Z
2015-09-12T08:00:00.000Z_2015-09-12T09:00:00.000Z
2015-09-12T09:00:00.000Z_2015-09-12T10:00:00.000Z
2015-09-12T10:00:00.000Z_2015-09-12T11:00:00.000Z
2015-09-12T11:00:00.000Z_2015-09-12T12:00:00.000Z
2015-09-12T12:00:00.000Z_2015-09-12T13:00:00.000Z
2015-09-12T13:00:00.000Z_2015-09-12T14:00:00.000Z
2015-09-12T14:00:00.000Z_2015-09-12T15:00:00.000Z
2015-09-12T15:00:00.000Z_2015-09-12T16:00:00.000Z
2015-09-12T16:00:00.000Z_2015-09-12T17:00:00.000Z
2015-09-12T17:00:00.000Z_2015-09-12T18:00:00.000Z
2015-09-12T18:00:00.000Z_2015-09-12T19:00:00.000Z
2015-09-12T19:00:00.000Z_2015-09-12T20:00:00.000Z
2015-09-12T20:00:00.000Z_2015-09-12T21:00:00.000Z
2015-09-12T21:00:00.000Z_2015-09-12T22:00:00.000Z
2015-09-12T22:00:00.000Z_2015-09-12T23:00:00.000Z
2015-09-12T23:00:00.000Z_2015-09-13T00:00:00.000Z
```
## Run a kill task
Now that we have disabled some segments, we can submit a Kill Task, which will delete the disabled segments from metadata and deep storage.
2018-11-02 00:47:29 -04:00
A Kill Task spec has been provided at `quickstart/tutorial/deletion-kill.json` . Submit this task to the Overlord with the following command:
2018-08-09 16:37:52 -04:00
2018-08-13 14:11:32 -04:00
```bash
2018-08-09 16:37:52 -04:00
curl -X 'POST' -H 'Content-Type:application/json' -d @quickstart/tutorial/deletion -kill.json http://localhost:8090/druid/indexer/v1/task
```
After this task completes, you can see that the disabled segments have now been removed from deep storage:
2018-08-13 14:11:32 -04:00
```bash
2018-08-09 16:37:52 -04:00
$ ls -l1 var/druid/segments/deletion-tutorial/
2015-09-12T12:00:00.000Z_2015-09-12T13:00:00.000Z
2015-09-12T15:00:00.000Z_2015-09-12T16:00:00.000Z
2015-09-12T16:00:00.000Z_2015-09-12T17:00:00.000Z
2015-09-12T17:00:00.000Z_2015-09-12T18:00:00.000Z
2015-09-12T20:00:00.000Z_2015-09-12T21:00:00.000Z
2015-09-12T21:00:00.000Z_2015-09-12T22:00:00.000Z
2015-09-12T22:00:00.000Z_2015-09-12T23:00:00.000Z
2015-09-12T23:00:00.000Z_2015-09-13T00:00:00.000Z
2018-11-13 12:38:37 -05:00
```