Update metalake

PUT 
/metalakes/:name

Applies one or more changes to a metalake, such as a rename, a new comment, or added or removed properties, and returns the updated metalake. The metalake must be in use.

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

updates

object[]

required

Array [

oneOf

RenameMetalakeRequest

@type stringrequired

Possible values: [rename]

newName stringrequired

The new name of the metalake

UpdateMetalakeCommentRequest

@type stringrequired

Possible values: [updateComment]

newComment stringrequired

The new comment of the metalake

SetMetalakePropertyRequest

@type stringrequired

Possible values: [setProperty]

property stringrequired

The property to set

value stringrequired

The value to set

RemoveMetalakePropertyRequest

@type stringrequired

Possible values: [removeProperty]

property stringrequired

The property to remove

]

Responses

200

The metalake, with its comment, properties and audit information.

application/vnd.gravitino.v1+json

Schema

Schema

code int32

Possible values: [0]

Status code of the response

metalake

object

Gravitino Metalake is the top-level metadata repository for users. It contains a list of catalogs as sub-level metadata collections. With GravitinoMetaLake, users can list, create, load, alter and drop a catalog with specified identifier.

name stringrequired

The name of the Metalake

comment stringnullable

A comment about the Metalake

audit

object

Audit information for a Gravitino resource.

creator string

The user who created the resource

createTime date-time

The time the resource was created

lastModifier string

The user who last modified the resource

lastModifiedTime date-time

The time the resource was last modified

properties

object

Configured string to string map of properties for the Metalake

property name* string

Example (from schema)

{
  "code": 0,
  "metalake": {
    "name": "my_metalake",
    "comment": "This is my metalake",
    "properties": {
      "key1": "value1",
      "key2": "value2",
      "in-use": "true"
    },
    "audit": {
      "creator": "gravitino",
      "createTime": "2023-12-07T14:04:17.349Z"
    }
  }
}

MetalakeResponse

{
  "code": 0,
  "metalake": {
    "name": "my_metalake",
    "comment": "This is my metalake",
    "properties": {
      "key1": "value1",
      "key2": "value2",
      "in-use": "true"
    },
    "audit": {
      "creator": "gravitino",
      "createTime": "2023-12-06T14:21:24.982Z"
    }
  }
}

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",
    "..."
  ]
}

409

A metalake with the new name already exists.

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"
}

MetalakeAlreadyExistsException

{
  "code": 1004,
  "type": "MetalakeAlreadyExistsException",
  "message": "Failed to operate metalake(s) [my_metalake] operation [CREATE], reason [MetalakeAlreadyExistsException]",
  "stack": [
    "org.apache.gravitino.exceptions.MetalakeAlreadyExistsException: Metalake my_metalake already exists",
    "..."
  ]
}

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