Associate tags with metadata object
POST/metalakes/:metalake/objects/:metadataObjectType/:metadataObjectFullName/tags
Associate tags with metadata object
Request
Path Parameters
The name of the metalake
Possible values: [CATALOG
, SCHEMA
, TABLE
, FILESET
, TOPIC
, ROLE
, METALAKE
]
The type of the metadata object
The full name of the metadata object
- application/json
Body
The tags to add
The tags to remove
Responses
- 200
- 409
- 5xx
Returns the list of tag names associated with the specified metadata object
- application/vnd.gravitino.v1+json
- Schema
- Example (from schema)
- NameListResponse
Schema
Possible values: [0
]
Status code of the response
{
"code": 0,
"names": [
"string"
]
}
{
"code": 0,
"names": [
"my_tag1",
"my_tag2"
]
}
Conflict - The target tag already associated with the specified metadata object
- application/vnd.gravitino.v1+json
- Schema
- Example (from schema)
- TagAlreadyAssociatedException
Schema
Possible values: >= 1000
and <= 1100
HTTP response code
Internal type definition of the error
A human-readable message
{
"code": 1002,
"type": "string",
"message": "string",
"stack": [
"string"
]
}
{
"code": 1004,
"type": "TagAlreadyAssociatedException",
"message": "Failed to operate tag(s) [my_tag] operation [ASSOCIATE] under metalake [my_test_metalake], reason [TagAlreadyAssociatedException]",
"stack": [
"org.apache.gravitino.exceptions.TagAlreadyAssociatedException: Tag my_tag already associated",
"..."
]
}
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.
- application/vnd.gravitino.v1+json
- Schema
- Example (from schema)
- Example
Schema
Possible values: >= 1000
and <= 1100
HTTP response code
Internal type definition of the error
A human-readable message
{
"code": 1002,
"type": "string",
"message": "string",
"stack": [
"string"
]
}
{
"code": 1002,
"type": "RuntimeException",
"message": "Internal Server Error",
"stack": [
"java.lang.RuntimeException: Internal Server Error"
]
}