Create a policy in the given namespace

post

{scheme}://{host}/{basePath}/polaris/v1/{prefix}/namespaces/{namespace}/policies

Creates a policy within the specified namespace.

A policy defines a set of rules governing actions on specified resources under predefined conditions.
In Apache Polaris, policies are created, stored, and later referenced by external engines to enforce access controls on associated resources.

User provides the following inputs when creating a policy

name (REQUIRED): The name of the policy.
type (REQUIRED): The type of the policy.
- Predefined Policies: policies have a system.* prefix in their type, such as system.data_compaction
description (OPTIONAL): Provides details about the policy's purpose and functionality
content (OPTIONAL): Defines the rules that control actions and access conditions on resources. The format can be JSON, SQL, or any other format.

The content field in the request body is validated using the policy's corresponding validator. The policy is created only if the content passes validation.

Upon successful creation, the new policy's version will be 0.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Responses

Language

Credentials

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200Policy object result after creating a policy

400Indicates 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.

401Unauthorized. The REST Catalog SHOULD respond with the 401 UnauthorizedResponse when the access token provided is expired, revoked, malformed, or invalid for other reasons. The client MAY request a new access token and retry the request.

403Forbidden. Authenticated user does not have the necessary permissions.

404Not Found - The namespace specified does not exist

409Conflict - The policy already exists under the given namespace

503The service is not ready to handle the request, request could have been partially processed. The service may additionally send a Retry-After header to indicate when to retry, a non idempotent request should only be retried by the client when the Retry-After header is present.

5XXA server-side problem that might not be addressable from the client side. Used for server 5xx errors without more specific documentation in individual routes.