Set metalake in use

PATCH 
/metalakes/:name

Marks a metalake as in use or not in use, which enables or disables it. A metalake that is not in use cannot be altered, and an in-use metalake cannot be dropped without force.

Sign in with a bearer token or a local user's password; see Authentication.

Request

Path Parameters

name stringrequired

The name of the metalake

application/json

Body

inUse booleanrequired

The in-use status of the metalake to set

Responses

200

The operation succeeded. The body carries only code, which is 0.

application/vnd.gravitino.v1+json

Schema

Schema

code int32required

Possible values: [0]

Status code of the response

Example (from schema)

{
  "code": 0
}

Example

{
  "code": 0
}

404

The metalake does not exist.

application/vnd.gravitino.v1+json

Schema

Schema

code integerrequired

Possible values: >= 1000 and <= 1100

HTTP response code

type stringrequired

Internal type definition of the error

message stringrequired

A human-readable message

stack string[]deprecated

Deprecated diagnostic stack trace. Enterprise omits it by default because it can expose internal implementation details. Operators can opt in for controlled diagnostics with gravitino.server.webserver.includeErrorStackTrace=true. See OWASP REST Security: Error handling and CWE-209.

Example (from schema)

{
  "code": 1002,
  "type": "string",
  "message": "string"
}

NoSuchMetalakeException

{
  "code": 1003,
  "type": "NoSuchMetalakeException",
  "message": "Failed to operate metalake(s) [test] operation [LOAD], reason [NoSuchMetalakeException]",
  "stack": [
    "org.apache.gravitino.exceptions.NoSuchMetalakeException: Metalake test does not exist",
    "..."
  ]
}

500

The server hit an internal error, such as a failure in its storage backend.

application/vnd.gravitino.v1+json

Schema

Schema

code integerrequired

Possible values: >= 1000 and <= 1100

HTTP response code

type stringrequired

Internal type definition of the error

message stringrequired

A human-readable message

stack string[]deprecated

Deprecated diagnostic stack trace. Enterprise omits it by default because it can expose internal implementation details. Operators can opt in for controlled diagnostics with gravitino.server.webserver.includeErrorStackTrace=true. See OWASP REST Security: Error handling and CWE-209.

Example (from schema)

{
  "code": 1002,
  "type": "string",
  "message": "string"
}

Loading...