Drop fileset
DELETE/metalakes/:metalake/catalogs/:catalog/schemas/:schema/filesets/:fileset
Drops a fileset and reports whether a fileset was dropped. Dropping a managed fileset also deletes the files at its storage locations unless the catalog sets disable-filesystem-ops to true, while dropping an external fileset leaves the files in place.
Sign in with a bearer token or a local user's password; see Authentication.
Request
Path Parameters
The name of the metalake
The name of the catalog
The name of the schema
The name of the fileset
Responses
- 200
- 400
- 403
- 406
- 5xx
Whether the object was dropped. dropped is false when the object did not exist or, for statistics, when none of the named statistics existed.
- application/vnd.gravitino.v1+json
- Schema
- Example (from schema)
- DropResponse
Schema
Possible values: [0]
Status code of the response
Whether the drop operation was successful
{
"code": 0,
"dropped": true
}
{
"code": 0,
"dropped": true
}
The request is malformed or fails validation, for example because of invalid JSON, a missing required field or an invalid parameter value. The body is normally an error model, although the server's middleware can return plain text instead.
- 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
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.
{
"code": 1002,
"type": "string",
"message": "string"
}
{
"code": 1003,
"type": "BadRequestException",
"message": "Malformed request"
}
The caller is not allowed to perform the operation. With authorization on, a metalake that does not exist, or that the caller is not a member of, also returns 403.
- 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
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.
{
"code": 1002,
"type": "string",
"message": "string"
}
{
"code": 1008,
"type": "ForbiddenException",
"message": "Current user alice is not a member of metalake metalake1, or the metalake does not exist"
}
The requested API version is not supported, or the operation cannot answer in the type the Accept header asks for. When Accept names no Gravitino API version, as with application/json, */*, or no header, the server takes the version from Content-Type if present, and the default version otherwise.
- 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
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.
{
"code": 1002,
"type": "string",
"message": "string"
}
{
"code": 1001,
"type": "IllegalArgumentException",
"message": "Unsupported version v99 in request header"
}
The server hit an internal error that the client usually cannot fix by changing the request.
- 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
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.
{
"code": 1002,
"type": "string",
"message": "string"
}
{
"code": 1002,
"type": "RuntimeException",
"message": "Internal Server Error",
"stack": [
"java.lang.RuntimeException: Internal Server Error"
]
}