---
title: "Remove columns from table"
method: POST
path: "/v1/table/{id}/drop_columns"
tags: ["Table", "Metadata"]
---

# Remove columns from table

`POST /v1/table/{id}/drop_columns`

Remove specified columns from table `id`.

## Path parameters

- `id` string, required

## Query parameters

- `delimiter` string

## Request body

- AlterTableDropColumnsRequest
  - `identity` Identity — Identity information of a request.
    - `api_key` string — API key for authentication. REST NAMESPACE ONLY This is passed via the `x-api-key` header.
    - `auth_token` string — Bearer token for authentication. REST NAMESPACE ONLY This is passed via the `Authorization` header with the Bearer scheme (e.g., `Bearer <token>`).
  - `context` unknown
  - `id` string[]
  - `branch` string — Branch to target. When not specified, the main branch is used.
  - `columns` string[], required — Lance field paths to drop. Nested fields use dot-separated segments; use backtick-quoted segments for literal dots and double backticks inside quoted segments. Use canonical full paths for display and errors; leaf names alone only identify top-level fields; invalid or unresolved paths should return InvalidInput or TableColumnNotFound.

## Response `200`

Drop columns operation result

- AlterTableDropColumnsResponse
  - `context` unknown
  - `transaction_id` string — Optional transaction identifier
  - `version` integer, required — Version of the table after dropping columns

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

> 54 revisions in range; 2 could not be searched.

- **2026-07-01** `591cd95574b0` — 7 info
  - added the optional property `context` to the response with the `200` status
  - added the optional property `context` to the response with the `400` status
  - added the optional property `context` to the response with the `401` status
  - added the optional property `context` to the response with the `403` status
  - …3 more
- **2026-06-10** `a3308034a3cd` — 1 breaking
  - the `columns/items/` request property's minLength was increased from `0` to `1`
- **2026-06-05** `9932582b6bd7` — 1 info
  - added the new optional request property `branch`
- **2026-01-02** `83f8516f0507` — 1 info
  - added the new optional request property `context`
- **2026-01-01** `c987c26ccb0f` — 1 info
  - added the new optional request property `identity`

[Full history](https://skmtc.dev/lance-format/apis/lance-namespace-specification/changes/v1/table/:id/drop_columns/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/541331733d0c/schema)