Create fileset
POST/metalakes/:metalake/catalogs/:catalog/schemas/:schema/filesets
Creates a fileset in the schema and returns it. An external fileset must have a storage location, while a managed fileset without one gets a location derived from the schema or catalog location property.
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
- application/json
Body
The name of the fileset. Can not be empty.
The type of the fileset. The value of type should be EXTERNAL or MANAGED
The comment of the fileset. Can be empty.
The location of the fileset. If the storage location of managed fileset is empty, it will \ use the location of namespace. The storage location of external fileset must be set.
storageLocations
object
nullable
The storage locations of the fileset. If the storage location of managed fileset is empty, \ it will use the location of namespace. The storage locations of external fileset must be set.
properties
object
nullable
The properties of the fileset. Can be empty.
Responses
- 200
- 409
- 5xx
The fileset, with its type, storage locations, comment, properties and audit information.
- application/vnd.gravitino.v1+json
- Schema
- Example (from schema)
- FilesetResponse
Schema
Possible values: [0]
Status code of the response
fileset
object
The name of the fileset
The type of the fileset
The comment of the fileset
The location of the fileset
storageLocations
object
The fileset's storage locations by location name. A location created without a name is listed as unknown.
properties
object
nullable
The properties of the fileset
audit
object
Audit information for a Gravitino resource.
The user who created the resource
The time the resource was created
The user who last modified the resource
The time the resource was last modified
{
"code": 0,
"fileset": {
"name": "string",
"type": "string",
"comment": "string",
"storageLocation": "string",
"storageLocations": {},
"properties": {},
"audit": {
"creator": "string",
"createTime": "2024-07-29T15:51:28.071Z",
"lastModifier": "string",
"lastModifiedTime": "2024-07-29T15:51:28.071Z"
}
}
}
{
"code": 0,
"fileset": {
"name": "fileset1",
"type": "managed",
"comment": "This is a comment",
"storageLocation": "hdfs://host/user/s_fileset/schema/fileset1",
"properties": {
"key1": "value1",
"key2": "value2"
}
}
}
A fileset with the same name already exists in the schema.
- application/vnd.gravitino.v1+json
- Schema
- Example (from schema)
- FilesetAlreadyExistsErrorResponse
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": 1004,
"type": "FilesetAlreadyExistsException",
"message": "Fileset already exists",
"stack": [
"java.lang.FilesetAlreadyExistsException: Fileset already exists"
]
}
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"
]
}