---
title: "Drop a namespace"
method: POST
path: "/v1/namespace/{id}/drop"
tags: ["Namespace", "Metadata"]
---

# Drop a namespace

`POST /v1/namespace/{id}/drop`

Drop namespace `id` from its parent namespace.

## Path parameters

- `id` string, required

## Query parameters

- `delimiter` string

## Request body

- DropNamespaceRequest
  - `id` string[]
  - `mode` 'SKIP' | 'FAIL' — The mode for dropping a namespace, deciding the server behavior when the namespace to drop is not found. - FAIL (default): the server must return 400 indicating the namespace to drop does not exist. - SKIP: the server must return 204 indicating the drop operation has succeeded.
  - `behavior` 'RESTRICT' | 'CASCADE' — The behavior for dropping a namespace. - RESTRICT (default): the namespace should not contain any table or child namespace when drop is initiated. If tables are found, the server should return error and not drop the namespace. - CASCADE: all tables and child namespaces in the namespace are dropped before the namespace is dropped.

## Response `200`

Result of dropping a namespace

- DropNamespaceResponse
  - `properties` unknown
  - `transaction_id` string[] — If present, indicating the operation is long running and should be tracked using GetTransaction

## Other responses

- `400` — Indicates a bad request error. It could be caused by an unexpected request body format or other forms of request validation failure, such as invalid json. Usually serves application/json content, although in some cases simple text/plain content might be returned by the server's middleware.
- `401` — Unauthorized. The request lacks valid authentication credentials for the operation.
- `403` — Forbidden. Authenticated user does not have the necessary permissions.
- `404` — A server-side problem that means can not find the specified resource.
- `409` — The request conflicts with the current state of the target resource.
- `503` — The service is not ready to handle the request. The client should wait and retry. The service may additionally send a Retry-After header to indicate when to retry.
- `5XX` — A server-side problem that might not be addressable from the client side. Used for server 5xx errors without more specific documentation in individual routes.

## Changes

- **2025-12-11** `6ad4337e3849` — 1 warning, 1 info
  - removed the optional property `transactionId` from the response with the `200` status
  - added the optional property `transaction_id` to the response with the `200` status
- **2025-07-29** `40a3bc489d46` — 7 breaking, 14 warning, 14 info
  - the response property `type` became optional for the status `400`
  - the response property `type` became optional for the status `401`
  - the response property `type` became optional for the status `403`
  - the response property `type` became optional for the status `404`
  - …31 more
- **2025-07-25** `8769f8e36bc4` — 1 breaking, 4 warning, 1 info
  - the `transactionId` response's property type changed from `string` to `array` for status `200`
  - removed the request property `name`
  - removed the request property `parent`
  - removed the optional property `name` from the response with the `200` status
  - …2 more
- **2025-07-22** `ac7519693c52` — 1 info
  - the request property `name` became optional
- **2025-07-21** `db7569410aa4` — 1 info
  - api tag `Metadata` added

[Full history](https://skmtc.dev/lance-format/apis/lance-namespace-specification/changes/v1/namespace/:id/drop/post.md)

---

[API](https://skmtc.dev/lance-format/apis/lance-namespace-specification.md) · [All operations](https://skmtc.dev/lance-format/apis/lance-namespace-specification/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/lance-format/lance-namespace-specification/revisions/6ad4337e3849/schema)