Replace a view
POST/v1/:prefix/namespaces/:namespace/views/:view
Commit updates to a view.
Request
Path Parameters
- singlepart_namespace
- multipart_namespace
The catalog name in Gravitino, as returned in defaults.prefix by GET /v1/config
A namespace identifier as a single string. Multipart namespace parts must be separated by the namespace separator as indicated via the /config override namespace-separator, which defaults to the unit separator 0x1F byte (url encoded %1F). To be compatible with older clients, servers must use both the advertised separator and 0x1F as valid separators when decoding namespaces. The namespace-separator should be provided in a url encoded form.
Example: accounting
Example: accounting%1Ftax
A view name
Header Parameters
- Finalize & replay: 200, 201, 204, and deterministic terminal 4xx (including 409 such as AlreadyExists, NamespaceNotEmpty, etc.)
- Do not finalize (not stored/replayed): 5xx
- Key format: UUIDv7 in string form (RFC 9562).
- The idempotency key must be globally unique (no reuse across different operations).
- Catalogs SHOULD NOT expire keys before the end of the advertised token lifetime.
- If Idempotency-Key is used, clients MUST reuse the same key when retrying the same logical operation and MUST generate a new key for a different operation.
Possible values: >= 36 characters and <= 36 characters
Optional client-provided idempotency key for safe request retries.
When present, the server ensures no additional effects for requests that carry the same Idempotency-Key. If a prior request with this key has been finalized, the server returns an equivalent final response without re-running the operation. The response body may reflect a newer state of the catalog than existed at the time of the commit.
Finalization rules:
Key Requirements:
- application/json
Body
required
Array [
- AssertViewUUID
]
Array [
- AssignUUIDUpdate
- UpgradeFormatVersionUpdate
- AddSchemaUpdate
- SetLocationUpdate
- SetPropertiesUpdate
- RemovePropertiesUpdate
- AddViewVersionUpdate
- SetCurrentViewVersionUpdate
- assign-uuid
- upgrade-format-version
- add-schema
- set-current-schema
- add-spec
- set-default-spec
- add-sort-order
- set-default-sort-order
- add-snapshot
- set-snapshot-ref
- remove-snapshots
- remove-snapshot-ref
- set-location
- set-properties
- remove-properties
- add-view-version
- set-current-view-version
- set-statistics
- remove-statistics
- set-partition-statistics
- remove-partition-statistics
- remove-partition-specs
- remove-schemas
- add-encryption-key
- remove-encryption-key
Array [
- PrimitiveType
- ListType
- MapType
- BooleanTypeValue
- IntegerTypeValue
- LongTypeValue
- FloatTypeValue
- DoubleTypeValue
- DecimalTypeValue
- StringTypeValue
- UUIDTypeValue
- DateTypeValue
- TimeTypeValue
- TimestampTypeValue
- TimestampTzTypeValue
- TimestampNanoTypeValue
- TimestampTzNanoTypeValue
- FixedTypeValue
- BinaryTypeValue
- BooleanTypeValue
- IntegerTypeValue
- LongTypeValue
- FloatTypeValue
- DoubleTypeValue
- DecimalTypeValue
- StringTypeValue
- UUIDTypeValue
- DateTypeValue
- TimeTypeValue
- TimestampTypeValue
- TimestampTzTypeValue
- TimestampNanoTypeValue
- TimestampTzNanoTypeValue
- FixedTypeValue
- BinaryTypeValue
]
Array [
]
Array [
]
Array [
- SQLViewRepresentation
]
Array [
]
- assign-uuid
- upgrade-format-version
- add-schema
- set-current-schema
- add-spec
- set-default-spec
- add-sort-order
- set-default-sort-order
- add-snapshot
- set-snapshot-ref
- remove-snapshots
- remove-snapshot-ref
- set-location
- set-properties
- remove-properties
- add-view-version
- set-current-view-version
- set-statistics
- remove-statistics
- set-partition-statistics
- remove-partition-statistics
- remove-partition-specs
- remove-schemas
- add-encryption-key
- remove-encryption-key
Array [
- PrimitiveType
- ListType
- MapType
- BooleanTypeValue
- IntegerTypeValue
- LongTypeValue
- FloatTypeValue
- DoubleTypeValue
- DecimalTypeValue
- StringTypeValue
- UUIDTypeValue
- DateTypeValue
- TimeTypeValue
- TimestampTypeValue
- TimestampTzTypeValue
- TimestampNanoTypeValue
- TimestampTzNanoTypeValue
- FixedTypeValue
- BinaryTypeValue
- BooleanTypeValue
- IntegerTypeValue
- LongTypeValue
- FloatTypeValue
- DoubleTypeValue
- DecimalTypeValue
- StringTypeValue
- UUIDTypeValue
- DateTypeValue
- TimeTypeValue
- TimestampTypeValue
- TimestampTzTypeValue
- TimestampNanoTypeValue
- TimestampTzNanoTypeValue
- FixedTypeValue
- BinaryTypeValue
]
Array [
]
Array [
]
Array [
- SQLViewRepresentation
]
Array [
]
Array [
- PrimitiveType
- ListType
- MapType
- BooleanTypeValue
- IntegerTypeValue
- LongTypeValue
- FloatTypeValue
- DoubleTypeValue
- DecimalTypeValue
- StringTypeValue
- UUIDTypeValue
- DateTypeValue
- TimeTypeValue
- TimestampTypeValue
- TimestampTzTypeValue
- TimestampNanoTypeValue
- TimestampTzNanoTypeValue
- FixedTypeValue
- BinaryTypeValue
- BooleanTypeValue
- IntegerTypeValue
- LongTypeValue
- FloatTypeValue
- DoubleTypeValue
- DecimalTypeValue
- StringTypeValue
- UUIDTypeValue
- DateTypeValue
- TimeTypeValue
- TimestampTypeValue
- TimestampTzTypeValue
- TimestampNanoTypeValue
- TimestampTzNanoTypeValue
- FixedTypeValue
- BinaryTypeValue
]
- assign-uuid
- upgrade-format-version
- add-schema
- set-current-schema
- add-spec
- set-default-spec
- add-sort-order
- set-default-sort-order
- add-snapshot
- set-snapshot-ref
- remove-snapshots
- remove-snapshot-ref
- set-location
- set-properties
- remove-properties
- add-view-version
- set-current-view-version
- set-statistics
- remove-statistics
- set-partition-statistics
- remove-partition-statistics
- remove-partition-specs
- remove-schemas
- add-encryption-key
- remove-encryption-key
Array [
]
Array [
]
Array [
- SQLViewRepresentation
]
Array [
]
- assign-uuid
- upgrade-format-version
- add-schema
- set-current-schema
- add-spec
- set-default-spec
- add-sort-order
- set-default-sort-order
- add-snapshot
- set-snapshot-ref
- remove-snapshots
- remove-snapshot-ref
- set-location
- set-properties
- remove-properties
- add-view-version
- set-current-view-version
- set-statistics
- remove-statistics
- set-partition-statistics
- remove-partition-statistics
- remove-partition-specs
- remove-schemas
- add-encryption-key
- remove-encryption-key
Array [
- PrimitiveType
- ListType
- MapType
- BooleanTypeValue
- IntegerTypeValue
- LongTypeValue
- FloatTypeValue
- DoubleTypeValue
- DecimalTypeValue
- StringTypeValue
- UUIDTypeValue
- DateTypeValue
- TimeTypeValue
- TimestampTypeValue
- TimestampTzTypeValue
- TimestampNanoTypeValue
- TimestampTzNanoTypeValue
- FixedTypeValue
- BinaryTypeValue
- BooleanTypeValue
- IntegerTypeValue
- LongTypeValue
- FloatTypeValue
- DoubleTypeValue
- DecimalTypeValue
- StringTypeValue
- UUIDTypeValue
- DateTypeValue
- TimeTypeValue
- TimestampTypeValue
- TimestampTzTypeValue
- TimestampNanoTypeValue
- TimestampTzNanoTypeValue
- FixedTypeValue
- BinaryTypeValue
]
Array [
]
Array [
]
Array [
- SQLViewRepresentation
]
Array [
]
- assign-uuid
- upgrade-format-version
- add-schema
- set-current-schema
- add-spec
- set-default-spec
- add-sort-order
- set-default-sort-order
- add-snapshot
- set-snapshot-ref
- remove-snapshots
- remove-snapshot-ref
- set-location
- set-properties
- remove-properties
- add-view-version
- set-current-view-version
- set-statistics
- remove-statistics
- set-partition-statistics
- remove-partition-statistics
- remove-partition-specs
- remove-schemas
- add-encryption-key
- remove-encryption-key
Array [
- PrimitiveType
- ListType
- MapType
- BooleanTypeValue
- IntegerTypeValue
- LongTypeValue
- FloatTypeValue
- DoubleTypeValue
- DecimalTypeValue
- StringTypeValue
- UUIDTypeValue
- DateTypeValue
- TimeTypeValue
- TimestampTypeValue
- TimestampTzTypeValue
- TimestampNanoTypeValue
- TimestampTzNanoTypeValue
- FixedTypeValue
- BinaryTypeValue
- BooleanTypeValue
- IntegerTypeValue
- LongTypeValue
- FloatTypeValue
- DoubleTypeValue
- DecimalTypeValue
- StringTypeValue
- UUIDTypeValue
- DateTypeValue
- TimeTypeValue
- TimestampTypeValue
- TimestampTzTypeValue
- TimestampNanoTypeValue
- TimestampTzNanoTypeValue
- FixedTypeValue
- BinaryTypeValue
]
Array [
]
Array [
]
Array [
- SQLViewRepresentation
]
Array [
]
- assign-uuid
- upgrade-format-version
- add-schema
- set-current-schema
- add-spec
- set-default-spec
- add-sort-order
- set-default-sort-order
- add-snapshot
- set-snapshot-ref
- remove-snapshots
- remove-snapshot-ref
- set-location
- set-properties
- remove-properties
- add-view-version
- set-current-view-version
- set-statistics
- remove-statistics
- set-partition-statistics
- remove-partition-statistics
- remove-partition-specs
- remove-schemas
- add-encryption-key
- remove-encryption-key
Array [
- PrimitiveType
- ListType
- MapType
- BooleanTypeValue
- IntegerTypeValue
- LongTypeValue
- FloatTypeValue
- DoubleTypeValue
- DecimalTypeValue
- StringTypeValue
- UUIDTypeValue
- DateTypeValue
- TimeTypeValue
- TimestampTypeValue
- TimestampTzTypeValue
- TimestampNanoTypeValue
- TimestampTzNanoTypeValue
- FixedTypeValue
- BinaryTypeValue
- BooleanTypeValue
- IntegerTypeValue
- LongTypeValue
- FloatTypeValue
- DoubleTypeValue
- DecimalTypeValue
- StringTypeValue
- UUIDTypeValue
- DateTypeValue
- TimeTypeValue
- TimestampTypeValue
- TimestampTzTypeValue
- TimestampNanoTypeValue
- TimestampTzNanoTypeValue
- FixedTypeValue
- BinaryTypeValue
]
Array [
]
Array [
]
Array [
- SQLViewRepresentation
]
Array [
]
Array [
- SQLViewRepresentation
]
- assign-uuid
- upgrade-format-version
- add-schema
- set-current-schema
- add-spec
- set-default-spec
- add-sort-order
- set-default-sort-order
- add-snapshot
- set-snapshot-ref
- remove-snapshots
- remove-snapshot-ref
- set-location
- set-properties
- remove-properties
- add-view-version
- set-current-view-version
- set-statistics
- remove-statistics
- set-partition-statistics
- remove-partition-statistics
- remove-partition-specs
- remove-schemas
- add-encryption-key
- remove-encryption-key
Array [
- PrimitiveType
- ListType
- MapType
- BooleanTypeValue
- IntegerTypeValue
- LongTypeValue
- FloatTypeValue
- DoubleTypeValue
- DecimalTypeValue
- StringTypeValue
- UUIDTypeValue
- DateTypeValue
- TimeTypeValue
- TimestampTypeValue
- TimestampTzTypeValue
- TimestampNanoTypeValue
- TimestampTzNanoTypeValue
- FixedTypeValue
- BinaryTypeValue
- BooleanTypeValue
- IntegerTypeValue
- LongTypeValue
- FloatTypeValue
- DoubleTypeValue
- DecimalTypeValue
- StringTypeValue
- UUIDTypeValue
- DateTypeValue
- TimeTypeValue
- TimestampTypeValue
- TimestampTzTypeValue
- TimestampNanoTypeValue
- TimestampTzNanoTypeValue
- FixedTypeValue
- BinaryTypeValue
]
Array [
]
Array [
]
Array [
]
- assign-uuid
- upgrade-format-version
- add-schema
- set-current-schema
- add-spec
- set-default-spec
- add-sort-order
- set-default-sort-order
- add-snapshot
- set-snapshot-ref
- remove-snapshots
- remove-snapshot-ref
- set-location
- set-properties
- remove-properties
- add-view-version
- set-current-view-version
- set-statistics
- remove-statistics
- set-partition-statistics
- remove-partition-statistics
- remove-partition-specs
- remove-schemas
- add-encryption-key
- remove-encryption-key
Array [
- PrimitiveType
- ListType
- MapType
- BooleanTypeValue
- IntegerTypeValue
- LongTypeValue
- FloatTypeValue
- DoubleTypeValue
- DecimalTypeValue
- StringTypeValue
- UUIDTypeValue
- DateTypeValue
- TimeTypeValue
- TimestampTypeValue
- TimestampTzTypeValue
- TimestampNanoTypeValue
- TimestampTzNanoTypeValue
- FixedTypeValue
- BinaryTypeValue
- BooleanTypeValue
- IntegerTypeValue
- LongTypeValue
- FloatTypeValue
- DoubleTypeValue
- DecimalTypeValue
- StringTypeValue
- UUIDTypeValue
- DateTypeValue
- TimeTypeValue
- TimestampTypeValue
- TimestampTzTypeValue
- TimestampNanoTypeValue
- TimestampTzNanoTypeValue
- FixedTypeValue
- BinaryTypeValue
]
Array [
]
Array [
]
Array [
- SQLViewRepresentation
]
Array [
]
]
identifier
object
View identifier to update
Reference to one or more levels of a namespace
requirements
object[]
oneOf
The view UUID must match the requirement's uuid
updates
object[]
required
anyOf
Assigning a UUID to a table/view should only be done when creating the table/view. It is not safe to re-assign the UUID if a table/view already has a UUID assigned
action
string
required
Possible values: [assign-uuid, upgrade-format-version, add-schema, set-current-schema, add-spec, set-default-spec, add-sort-order, set-default-sort-order, add-snapshot, set-snapshot-ref, remove-snapshots, remove-snapshot-ref, set-location, set-properties, remove-properties, add-view-version, set-current-view-version, set-statistics, remove-statistics, set-partition-statistics, remove-partition-statistics, remove-partition-specs, remove-schemas, add-encryption-key, remove-encryption-key]
circular(AssignUUIDUpdate)
schema
object
required
fields
object[]
required
type
object
required
oneOf
string
initial-default
object
oneOf
boolean
integer
integer
number
number
Decimal type values are serialized as strings. Decimals with a positive scale serialize as numeric plain text, while decimals with a negative scale use scientific notation and the exponent will be equal to the negated scale. For instance, a decimal with a positive scale is '123.4500', with zero scale is '2', and with a negative scale is '2E+20'
string
string
UUID type values are serialized as a 36-character lowercase string in standard UUID format as specified by RFC-4122
string
Possible values: >= 36 characters and <= 36 characters, Value must match regular expression ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Date type values follow the 'YYYY-MM-DD' ISO-8601 standard date format
string
Time type values follow the 'HH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
Timestamp type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
TimestampTz type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss+00:00' ISO-8601 format with microsecond precision, and a timezone offset (+00:00 for UTC)
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss' ISO-8601 format with nanosecond precision
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss+00:00' ISO-8601 format with nanosecond precision, and a timezone offset (+00:00 for UTC)
string
Fixed length type values are stored and serialized as an uppercase hexadecimal string preserving the fixed length
string
Binary type values are stored and serialized as an uppercase hexadecimal string
string
write-default
object
oneOf
boolean
integer
integer
number
number
Decimal type values are serialized as strings. Decimals with a positive scale serialize as numeric plain text, while decimals with a negative scale use scientific notation and the exponent will be equal to the negated scale. For instance, a decimal with a positive scale is '123.4500', with zero scale is '2', and with a negative scale is '2E+20'
string
string
UUID type values are serialized as a 36-character lowercase string in standard UUID format as specified by RFC-4122
string
Possible values: >= 36 characters and <= 36 characters, Value must match regular expression ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Date type values follow the 'YYYY-MM-DD' ISO-8601 standard date format
string
Time type values follow the 'HH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
Timestamp type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
TimestampTz type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss+00:00' ISO-8601 format with microsecond precision, and a timezone offset (+00:00 for UTC)
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss' ISO-8601 format with nanosecond precision
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss+00:00' ISO-8601 format with nanosecond precision, and a timezone offset (+00:00 for UTC)
string
Fixed length type values are stored and serialized as an uppercase hexadecimal string preserving the fixed length
string
Binary type values are stored and serialized as an uppercase hexadecimal string
string
This optional field is DEPRECATED for REMOVAL since it more safe to handle this internally, and shouldn't be exposed to the clients. The highest assigned column ID for the table. This is used to ensure columns are always assigned an unused ID when evolving schemas. When omitted, it will be computed on the server side.
Schema ID to set as current, or -1 to set last added schema
spec
object
required
fields
object[]
required
Partition spec ID to set as the default, or -1 to set last added spec
sort-order
object
required
fields
object[]
required
Possible values: [asc, desc]
Possible values: [nulls-first, nulls-last]
Sort order ID to set as the default, or -1 to set last added sort order
snapshot
object
required
Location of the snapshot's manifest list file
The first _row_id assigned to the first row in the first data file in the first manifest
The upper bound of the number of rows with assigned row IDs
summary
object
required
Possible values: [append, replace, overwrite, delete]
Possible values: [tag, branch]
updates
object
required
view-version
object
required
Schema ID to set as current, or -1 to set last added schema
summary
object
required
representations
object[]
required
oneOf
Reference to one or more levels of a namespace
The view version id to set as current, or -1 to set last added view version id
This optional field is DEPRECATED for REMOVAL since it contains redundant information. Clients should use the statistics.snapshot-id field instead.
statistics
object
required
blob-metadata
object[]
required
properties
object
partition-statistics
object
required
encryption-key
object
required
properties
object
action
string
required
Possible values: [assign-uuid, upgrade-format-version, add-schema, set-current-schema, add-spec, set-default-spec, add-sort-order, set-default-sort-order, add-snapshot, set-snapshot-ref, remove-snapshots, remove-snapshot-ref, set-location, set-properties, remove-properties, add-view-version, set-current-view-version, set-statistics, remove-statistics, set-partition-statistics, remove-partition-statistics, remove-partition-specs, remove-schemas, add-encryption-key, remove-encryption-key]
circular(UpgradeFormatVersionUpdate)
schema
object
required
fields
object[]
required
type
object
required
oneOf
string
initial-default
object
oneOf
boolean
integer
integer
number
number
Decimal type values are serialized as strings. Decimals with a positive scale serialize as numeric plain text, while decimals with a negative scale use scientific notation and the exponent will be equal to the negated scale. For instance, a decimal with a positive scale is '123.4500', with zero scale is '2', and with a negative scale is '2E+20'
string
string
UUID type values are serialized as a 36-character lowercase string in standard UUID format as specified by RFC-4122
string
Possible values: >= 36 characters and <= 36 characters, Value must match regular expression ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Date type values follow the 'YYYY-MM-DD' ISO-8601 standard date format
string
Time type values follow the 'HH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
Timestamp type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
TimestampTz type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss+00:00' ISO-8601 format with microsecond precision, and a timezone offset (+00:00 for UTC)
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss' ISO-8601 format with nanosecond precision
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss+00:00' ISO-8601 format with nanosecond precision, and a timezone offset (+00:00 for UTC)
string
Fixed length type values are stored and serialized as an uppercase hexadecimal string preserving the fixed length
string
Binary type values are stored and serialized as an uppercase hexadecimal string
string
write-default
object
oneOf
boolean
integer
integer
number
number
Decimal type values are serialized as strings. Decimals with a positive scale serialize as numeric plain text, while decimals with a negative scale use scientific notation and the exponent will be equal to the negated scale. For instance, a decimal with a positive scale is '123.4500', with zero scale is '2', and with a negative scale is '2E+20'
string
string
UUID type values are serialized as a 36-character lowercase string in standard UUID format as specified by RFC-4122
string
Possible values: >= 36 characters and <= 36 characters, Value must match regular expression ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Date type values follow the 'YYYY-MM-DD' ISO-8601 standard date format
string
Time type values follow the 'HH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
Timestamp type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
TimestampTz type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss+00:00' ISO-8601 format with microsecond precision, and a timezone offset (+00:00 for UTC)
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss' ISO-8601 format with nanosecond precision
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss+00:00' ISO-8601 format with nanosecond precision, and a timezone offset (+00:00 for UTC)
string
Fixed length type values are stored and serialized as an uppercase hexadecimal string preserving the fixed length
string
Binary type values are stored and serialized as an uppercase hexadecimal string
string
This optional field is DEPRECATED for REMOVAL since it more safe to handle this internally, and shouldn't be exposed to the clients. The highest assigned column ID for the table. This is used to ensure columns are always assigned an unused ID when evolving schemas. When omitted, it will be computed on the server side.
Schema ID to set as current, or -1 to set last added schema
spec
object
required
fields
object[]
required
Partition spec ID to set as the default, or -1 to set last added spec
sort-order
object
required
fields
object[]
required
Possible values: [asc, desc]
Possible values: [nulls-first, nulls-last]
Sort order ID to set as the default, or -1 to set last added sort order
snapshot
object
required
Location of the snapshot's manifest list file
The first _row_id assigned to the first row in the first data file in the first manifest
The upper bound of the number of rows with assigned row IDs
summary
object
required
Possible values: [append, replace, overwrite, delete]
Possible values: [tag, branch]
updates
object
required
view-version
object
required
Schema ID to set as current, or -1 to set last added schema
summary
object
required
representations
object[]
required
oneOf
Reference to one or more levels of a namespace
The view version id to set as current, or -1 to set last added view version id
This optional field is DEPRECATED for REMOVAL since it contains redundant information. Clients should use the statistics.snapshot-id field instead.
statistics
object
required
blob-metadata
object[]
required
properties
object
partition-statistics
object
required
encryption-key
object
required
properties
object
schema
object
required
fields
object[]
required
type
object
required
oneOf
string
initial-default
object
oneOf
boolean
integer
integer
number
number
Decimal type values are serialized as strings. Decimals with a positive scale serialize as numeric plain text, while decimals with a negative scale use scientific notation and the exponent will be equal to the negated scale. For instance, a decimal with a positive scale is '123.4500', with zero scale is '2', and with a negative scale is '2E+20'
string
string
UUID type values are serialized as a 36-character lowercase string in standard UUID format as specified by RFC-4122
string
Possible values: >= 36 characters and <= 36 characters, Value must match regular expression ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Date type values follow the 'YYYY-MM-DD' ISO-8601 standard date format
string
Time type values follow the 'HH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
Timestamp type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
TimestampTz type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss+00:00' ISO-8601 format with microsecond precision, and a timezone offset (+00:00 for UTC)
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss' ISO-8601 format with nanosecond precision
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss+00:00' ISO-8601 format with nanosecond precision, and a timezone offset (+00:00 for UTC)
string
Fixed length type values are stored and serialized as an uppercase hexadecimal string preserving the fixed length
string
Binary type values are stored and serialized as an uppercase hexadecimal string
string
write-default
object
oneOf
boolean
integer
integer
number
number
Decimal type values are serialized as strings. Decimals with a positive scale serialize as numeric plain text, while decimals with a negative scale use scientific notation and the exponent will be equal to the negated scale. For instance, a decimal with a positive scale is '123.4500', with zero scale is '2', and with a negative scale is '2E+20'
string
string
UUID type values are serialized as a 36-character lowercase string in standard UUID format as specified by RFC-4122
string
Possible values: >= 36 characters and <= 36 characters, Value must match regular expression ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Date type values follow the 'YYYY-MM-DD' ISO-8601 standard date format
string
Time type values follow the 'HH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
Timestamp type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
TimestampTz type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss+00:00' ISO-8601 format with microsecond precision, and a timezone offset (+00:00 for UTC)
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss' ISO-8601 format with nanosecond precision
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss+00:00' ISO-8601 format with nanosecond precision, and a timezone offset (+00:00 for UTC)
string
Fixed length type values are stored and serialized as an uppercase hexadecimal string preserving the fixed length
string
Binary type values are stored and serialized as an uppercase hexadecimal string
string
This optional field is DEPRECATED for REMOVAL since it more safe to handle this internally, and shouldn't be exposed to the clients. The highest assigned column ID for the table. This is used to ensure columns are always assigned an unused ID when evolving schemas. When omitted, it will be computed on the server side.
action
string
required
Possible values: [assign-uuid, upgrade-format-version, add-schema, set-current-schema, add-spec, set-default-spec, add-sort-order, set-default-sort-order, add-snapshot, set-snapshot-ref, remove-snapshots, remove-snapshot-ref, set-location, set-properties, remove-properties, add-view-version, set-current-view-version, set-statistics, remove-statistics, set-partition-statistics, remove-partition-statistics, remove-partition-specs, remove-schemas, add-encryption-key, remove-encryption-key]
circular(AddSchemaUpdate)
Schema ID to set as current, or -1 to set last added schema
spec
object
required
fields
object[]
required
Partition spec ID to set as the default, or -1 to set last added spec
sort-order
object
required
fields
object[]
required
Possible values: [asc, desc]
Possible values: [nulls-first, nulls-last]
Sort order ID to set as the default, or -1 to set last added sort order
snapshot
object
required
Location of the snapshot's manifest list file
The first _row_id assigned to the first row in the first data file in the first manifest
The upper bound of the number of rows with assigned row IDs
summary
object
required
Possible values: [append, replace, overwrite, delete]
Possible values: [tag, branch]
updates
object
required
view-version
object
required
Schema ID to set as current, or -1 to set last added schema
summary
object
required
representations
object[]
required
oneOf
Reference to one or more levels of a namespace
The view version id to set as current, or -1 to set last added view version id
This optional field is DEPRECATED for REMOVAL since it contains redundant information. Clients should use the statistics.snapshot-id field instead.
statistics
object
required
blob-metadata
object[]
required
properties
object
partition-statistics
object
required
encryption-key
object
required
properties
object
action
string
required
Possible values: [assign-uuid, upgrade-format-version, add-schema, set-current-schema, add-spec, set-default-spec, add-sort-order, set-default-sort-order, add-snapshot, set-snapshot-ref, remove-snapshots, remove-snapshot-ref, set-location, set-properties, remove-properties, add-view-version, set-current-view-version, set-statistics, remove-statistics, set-partition-statistics, remove-partition-statistics, remove-partition-specs, remove-schemas, add-encryption-key, remove-encryption-key]
schema
object
required
fields
object[]
required
type
object
required
oneOf
string
initial-default
object
oneOf
boolean
integer
integer
number
number
Decimal type values are serialized as strings. Decimals with a positive scale serialize as numeric plain text, while decimals with a negative scale use scientific notation and the exponent will be equal to the negated scale. For instance, a decimal with a positive scale is '123.4500', with zero scale is '2', and with a negative scale is '2E+20'
string
string
UUID type values are serialized as a 36-character lowercase string in standard UUID format as specified by RFC-4122
string
Possible values: >= 36 characters and <= 36 characters, Value must match regular expression ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Date type values follow the 'YYYY-MM-DD' ISO-8601 standard date format
string
Time type values follow the 'HH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
Timestamp type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
TimestampTz type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss+00:00' ISO-8601 format with microsecond precision, and a timezone offset (+00:00 for UTC)
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss' ISO-8601 format with nanosecond precision
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss+00:00' ISO-8601 format with nanosecond precision, and a timezone offset (+00:00 for UTC)
string
Fixed length type values are stored and serialized as an uppercase hexadecimal string preserving the fixed length
string
Binary type values are stored and serialized as an uppercase hexadecimal string
string
write-default
object
oneOf
boolean
integer
integer
number
number
Decimal type values are serialized as strings. Decimals with a positive scale serialize as numeric plain text, while decimals with a negative scale use scientific notation and the exponent will be equal to the negated scale. For instance, a decimal with a positive scale is '123.4500', with zero scale is '2', and with a negative scale is '2E+20'
string
string
UUID type values are serialized as a 36-character lowercase string in standard UUID format as specified by RFC-4122
string
Possible values: >= 36 characters and <= 36 characters, Value must match regular expression ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Date type values follow the 'YYYY-MM-DD' ISO-8601 standard date format
string
Time type values follow the 'HH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
Timestamp type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
TimestampTz type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss+00:00' ISO-8601 format with microsecond precision, and a timezone offset (+00:00 for UTC)
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss' ISO-8601 format with nanosecond precision
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss+00:00' ISO-8601 format with nanosecond precision, and a timezone offset (+00:00 for UTC)
string
Fixed length type values are stored and serialized as an uppercase hexadecimal string preserving the fixed length
string
Binary type values are stored and serialized as an uppercase hexadecimal string
string
This optional field is DEPRECATED for REMOVAL since it more safe to handle this internally, and shouldn't be exposed to the clients. The highest assigned column ID for the table. This is used to ensure columns are always assigned an unused ID when evolving schemas. When omitted, it will be computed on the server side.
Schema ID to set as current, or -1 to set last added schema
spec
object
required
fields
object[]
required
Partition spec ID to set as the default, or -1 to set last added spec
sort-order
object
required
fields
object[]
required
Possible values: [asc, desc]
Possible values: [nulls-first, nulls-last]
Sort order ID to set as the default, or -1 to set last added sort order
snapshot
object
required
Location of the snapshot's manifest list file
The first _row_id assigned to the first row in the first data file in the first manifest
The upper bound of the number of rows with assigned row IDs
summary
object
required
Possible values: [append, replace, overwrite, delete]
Possible values: [tag, branch]
circular(SetLocationUpdate)
updates
object
required
view-version
object
required
Schema ID to set as current, or -1 to set last added schema
summary
object
required
representations
object[]
required
oneOf
Reference to one or more levels of a namespace
The view version id to set as current, or -1 to set last added view version id
This optional field is DEPRECATED for REMOVAL since it contains redundant information. Clients should use the statistics.snapshot-id field instead.
statistics
object
required
blob-metadata
object[]
required
properties
object
partition-statistics
object
required
encryption-key
object
required
properties
object
updates
object
required
action
string
required
Possible values: [assign-uuid, upgrade-format-version, add-schema, set-current-schema, add-spec, set-default-spec, add-sort-order, set-default-sort-order, add-snapshot, set-snapshot-ref, remove-snapshots, remove-snapshot-ref, set-location, set-properties, remove-properties, add-view-version, set-current-view-version, set-statistics, remove-statistics, set-partition-statistics, remove-partition-statistics, remove-partition-specs, remove-schemas, add-encryption-key, remove-encryption-key]
schema
object
required
fields
object[]
required
type
object
required
oneOf
string
initial-default
object
oneOf
boolean
integer
integer
number
number
Decimal type values are serialized as strings. Decimals with a positive scale serialize as numeric plain text, while decimals with a negative scale use scientific notation and the exponent will be equal to the negated scale. For instance, a decimal with a positive scale is '123.4500', with zero scale is '2', and with a negative scale is '2E+20'
string
string
UUID type values are serialized as a 36-character lowercase string in standard UUID format as specified by RFC-4122
string
Possible values: >= 36 characters and <= 36 characters, Value must match regular expression ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Date type values follow the 'YYYY-MM-DD' ISO-8601 standard date format
string
Time type values follow the 'HH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
Timestamp type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
TimestampTz type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss+00:00' ISO-8601 format with microsecond precision, and a timezone offset (+00:00 for UTC)
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss' ISO-8601 format with nanosecond precision
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss+00:00' ISO-8601 format with nanosecond precision, and a timezone offset (+00:00 for UTC)
string
Fixed length type values are stored and serialized as an uppercase hexadecimal string preserving the fixed length
string
Binary type values are stored and serialized as an uppercase hexadecimal string
string
write-default
object
oneOf
boolean
integer
integer
number
number
Decimal type values are serialized as strings. Decimals with a positive scale serialize as numeric plain text, while decimals with a negative scale use scientific notation and the exponent will be equal to the negated scale. For instance, a decimal with a positive scale is '123.4500', with zero scale is '2', and with a negative scale is '2E+20'
string
string
UUID type values are serialized as a 36-character lowercase string in standard UUID format as specified by RFC-4122
string
Possible values: >= 36 characters and <= 36 characters, Value must match regular expression ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Date type values follow the 'YYYY-MM-DD' ISO-8601 standard date format
string
Time type values follow the 'HH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
Timestamp type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
TimestampTz type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss+00:00' ISO-8601 format with microsecond precision, and a timezone offset (+00:00 for UTC)
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss' ISO-8601 format with nanosecond precision
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss+00:00' ISO-8601 format with nanosecond precision, and a timezone offset (+00:00 for UTC)
string
Fixed length type values are stored and serialized as an uppercase hexadecimal string preserving the fixed length
string
Binary type values are stored and serialized as an uppercase hexadecimal string
string
This optional field is DEPRECATED for REMOVAL since it more safe to handle this internally, and shouldn't be exposed to the clients. The highest assigned column ID for the table. This is used to ensure columns are always assigned an unused ID when evolving schemas. When omitted, it will be computed on the server side.
Schema ID to set as current, or -1 to set last added schema
spec
object
required
fields
object[]
required
Partition spec ID to set as the default, or -1 to set last added spec
sort-order
object
required
fields
object[]
required
Possible values: [asc, desc]
Possible values: [nulls-first, nulls-last]
Sort order ID to set as the default, or -1 to set last added sort order
snapshot
object
required
Location of the snapshot's manifest list file
The first _row_id assigned to the first row in the first data file in the first manifest
The upper bound of the number of rows with assigned row IDs
summary
object
required
Possible values: [append, replace, overwrite, delete]
Possible values: [tag, branch]
circular(SetPropertiesUpdate)
view-version
object
required
Schema ID to set as current, or -1 to set last added schema
summary
object
required
representations
object[]
required
oneOf
Reference to one or more levels of a namespace
The view version id to set as current, or -1 to set last added view version id
This optional field is DEPRECATED for REMOVAL since it contains redundant information. Clients should use the statistics.snapshot-id field instead.
statistics
object
required
blob-metadata
object[]
required
properties
object
partition-statistics
object
required
encryption-key
object
required
properties
object
action
string
required
Possible values: [assign-uuid, upgrade-format-version, add-schema, set-current-schema, add-spec, set-default-spec, add-sort-order, set-default-sort-order, add-snapshot, set-snapshot-ref, remove-snapshots, remove-snapshot-ref, set-location, set-properties, remove-properties, add-view-version, set-current-view-version, set-statistics, remove-statistics, set-partition-statistics, remove-partition-statistics, remove-partition-specs, remove-schemas, add-encryption-key, remove-encryption-key]
schema
object
required
fields
object[]
required
type
object
required
oneOf
string
initial-default
object
oneOf
boolean
integer
integer
number
number
Decimal type values are serialized as strings. Decimals with a positive scale serialize as numeric plain text, while decimals with a negative scale use scientific notation and the exponent will be equal to the negated scale. For instance, a decimal with a positive scale is '123.4500', with zero scale is '2', and with a negative scale is '2E+20'
string
string
UUID type values are serialized as a 36-character lowercase string in standard UUID format as specified by RFC-4122
string
Possible values: >= 36 characters and <= 36 characters, Value must match regular expression ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Date type values follow the 'YYYY-MM-DD' ISO-8601 standard date format
string
Time type values follow the 'HH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
Timestamp type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
TimestampTz type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss+00:00' ISO-8601 format with microsecond precision, and a timezone offset (+00:00 for UTC)
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss' ISO-8601 format with nanosecond precision
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss+00:00' ISO-8601 format with nanosecond precision, and a timezone offset (+00:00 for UTC)
string
Fixed length type values are stored and serialized as an uppercase hexadecimal string preserving the fixed length
string
Binary type values are stored and serialized as an uppercase hexadecimal string
string
write-default
object
oneOf
boolean
integer
integer
number
number
Decimal type values are serialized as strings. Decimals with a positive scale serialize as numeric plain text, while decimals with a negative scale use scientific notation and the exponent will be equal to the negated scale. For instance, a decimal with a positive scale is '123.4500', with zero scale is '2', and with a negative scale is '2E+20'
string
string
UUID type values are serialized as a 36-character lowercase string in standard UUID format as specified by RFC-4122
string
Possible values: >= 36 characters and <= 36 characters, Value must match regular expression ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Date type values follow the 'YYYY-MM-DD' ISO-8601 standard date format
string
Time type values follow the 'HH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
Timestamp type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
TimestampTz type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss+00:00' ISO-8601 format with microsecond precision, and a timezone offset (+00:00 for UTC)
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss' ISO-8601 format with nanosecond precision
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss+00:00' ISO-8601 format with nanosecond precision, and a timezone offset (+00:00 for UTC)
string
Fixed length type values are stored and serialized as an uppercase hexadecimal string preserving the fixed length
string
Binary type values are stored and serialized as an uppercase hexadecimal string
string
This optional field is DEPRECATED for REMOVAL since it more safe to handle this internally, and shouldn't be exposed to the clients. The highest assigned column ID for the table. This is used to ensure columns are always assigned an unused ID when evolving schemas. When omitted, it will be computed on the server side.
Schema ID to set as current, or -1 to set last added schema
spec
object
required
fields
object[]
required
Partition spec ID to set as the default, or -1 to set last added spec
sort-order
object
required
fields
object[]
required
Possible values: [asc, desc]
Possible values: [nulls-first, nulls-last]
Sort order ID to set as the default, or -1 to set last added sort order
snapshot
object
required
Location of the snapshot's manifest list file
The first _row_id assigned to the first row in the first data file in the first manifest
The upper bound of the number of rows with assigned row IDs
summary
object
required
Possible values: [append, replace, overwrite, delete]
Possible values: [tag, branch]
updates
object
required
circular(RemovePropertiesUpdate)
view-version
object
required
Schema ID to set as current, or -1 to set last added schema
summary
object
required
representations
object[]
required
oneOf
Reference to one or more levels of a namespace
The view version id to set as current, or -1 to set last added view version id
This optional field is DEPRECATED for REMOVAL since it contains redundant information. Clients should use the statistics.snapshot-id field instead.
statistics
object
required
blob-metadata
object[]
required
properties
object
partition-statistics
object
required
encryption-key
object
required
properties
object
view-version
object
required
Schema ID to set as current, or -1 to set last added schema
summary
object
required
representations
object[]
required
oneOf
Reference to one or more levels of a namespace
action
string
required
Possible values: [assign-uuid, upgrade-format-version, add-schema, set-current-schema, add-spec, set-default-spec, add-sort-order, set-default-sort-order, add-snapshot, set-snapshot-ref, remove-snapshots, remove-snapshot-ref, set-location, set-properties, remove-properties, add-view-version, set-current-view-version, set-statistics, remove-statistics, set-partition-statistics, remove-partition-statistics, remove-partition-specs, remove-schemas, add-encryption-key, remove-encryption-key]
schema
object
required
fields
object[]
required
type
object
required
oneOf
string
initial-default
object
oneOf
boolean
integer
integer
number
number
Decimal type values are serialized as strings. Decimals with a positive scale serialize as numeric plain text, while decimals with a negative scale use scientific notation and the exponent will be equal to the negated scale. For instance, a decimal with a positive scale is '123.4500', with zero scale is '2', and with a negative scale is '2E+20'
string
string
UUID type values are serialized as a 36-character lowercase string in standard UUID format as specified by RFC-4122
string
Possible values: >= 36 characters and <= 36 characters, Value must match regular expression ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Date type values follow the 'YYYY-MM-DD' ISO-8601 standard date format
string
Time type values follow the 'HH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
Timestamp type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
TimestampTz type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss+00:00' ISO-8601 format with microsecond precision, and a timezone offset (+00:00 for UTC)
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss' ISO-8601 format with nanosecond precision
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss+00:00' ISO-8601 format with nanosecond precision, and a timezone offset (+00:00 for UTC)
string
Fixed length type values are stored and serialized as an uppercase hexadecimal string preserving the fixed length
string
Binary type values are stored and serialized as an uppercase hexadecimal string
string
write-default
object
oneOf
boolean
integer
integer
number
number
Decimal type values are serialized as strings. Decimals with a positive scale serialize as numeric plain text, while decimals with a negative scale use scientific notation and the exponent will be equal to the negated scale. For instance, a decimal with a positive scale is '123.4500', with zero scale is '2', and with a negative scale is '2E+20'
string
string
UUID type values are serialized as a 36-character lowercase string in standard UUID format as specified by RFC-4122
string
Possible values: >= 36 characters and <= 36 characters, Value must match regular expression ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Date type values follow the 'YYYY-MM-DD' ISO-8601 standard date format
string
Time type values follow the 'HH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
Timestamp type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
TimestampTz type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss+00:00' ISO-8601 format with microsecond precision, and a timezone offset (+00:00 for UTC)
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss' ISO-8601 format with nanosecond precision
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss+00:00' ISO-8601 format with nanosecond precision, and a timezone offset (+00:00 for UTC)
string
Fixed length type values are stored and serialized as an uppercase hexadecimal string preserving the fixed length
string
Binary type values are stored and serialized as an uppercase hexadecimal string
string
This optional field is DEPRECATED for REMOVAL since it more safe to handle this internally, and shouldn't be exposed to the clients. The highest assigned column ID for the table. This is used to ensure columns are always assigned an unused ID when evolving schemas. When omitted, it will be computed on the server side.
Schema ID to set as current, or -1 to set last added schema
spec
object
required
fields
object[]
required
Partition spec ID to set as the default, or -1 to set last added spec
sort-order
object
required
fields
object[]
required
Possible values: [asc, desc]
Possible values: [nulls-first, nulls-last]
Sort order ID to set as the default, or -1 to set last added sort order
snapshot
object
required
Location of the snapshot's manifest list file
The first _row_id assigned to the first row in the first data file in the first manifest
The upper bound of the number of rows with assigned row IDs
summary
object
required
Possible values: [append, replace, overwrite, delete]
Possible values: [tag, branch]
updates
object
required
circular(AddViewVersionUpdate)
The view version id to set as current, or -1 to set last added view version id
This optional field is DEPRECATED for REMOVAL since it contains redundant information. Clients should use the statistics.snapshot-id field instead.
statistics
object
required
blob-metadata
object[]
required
properties
object
partition-statistics
object
required
encryption-key
object
required
properties
object
The view version id to set as current, or -1 to set last added view version id
action
string
required
Possible values: [assign-uuid, upgrade-format-version, add-schema, set-current-schema, add-spec, set-default-spec, add-sort-order, set-default-sort-order, add-snapshot, set-snapshot-ref, remove-snapshots, remove-snapshot-ref, set-location, set-properties, remove-properties, add-view-version, set-current-view-version, set-statistics, remove-statistics, set-partition-statistics, remove-partition-statistics, remove-partition-specs, remove-schemas, add-encryption-key, remove-encryption-key]
schema
object
required
fields
object[]
required
type
object
required
oneOf
string
initial-default
object
oneOf
boolean
integer
integer
number
number
Decimal type values are serialized as strings. Decimals with a positive scale serialize as numeric plain text, while decimals with a negative scale use scientific notation and the exponent will be equal to the negated scale. For instance, a decimal with a positive scale is '123.4500', with zero scale is '2', and with a negative scale is '2E+20'
string
string
UUID type values are serialized as a 36-character lowercase string in standard UUID format as specified by RFC-4122
string
Possible values: >= 36 characters and <= 36 characters, Value must match regular expression ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Date type values follow the 'YYYY-MM-DD' ISO-8601 standard date format
string
Time type values follow the 'HH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
Timestamp type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
TimestampTz type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss+00:00' ISO-8601 format with microsecond precision, and a timezone offset (+00:00 for UTC)
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss' ISO-8601 format with nanosecond precision
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss+00:00' ISO-8601 format with nanosecond precision, and a timezone offset (+00:00 for UTC)
string
Fixed length type values are stored and serialized as an uppercase hexadecimal string preserving the fixed length
string
Binary type values are stored and serialized as an uppercase hexadecimal string
string
write-default
object
oneOf
boolean
integer
integer
number
number
Decimal type values are serialized as strings. Decimals with a positive scale serialize as numeric plain text, while decimals with a negative scale use scientific notation and the exponent will be equal to the negated scale. For instance, a decimal with a positive scale is '123.4500', with zero scale is '2', and with a negative scale is '2E+20'
string
string
UUID type values are serialized as a 36-character lowercase string in standard UUID format as specified by RFC-4122
string
Possible values: >= 36 characters and <= 36 characters, Value must match regular expression ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$
Date type values follow the 'YYYY-MM-DD' ISO-8601 standard date format
string
Time type values follow the 'HH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
Timestamp type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss' ISO-8601 format with microsecond precision
string
TimestampTz type values follow the 'YYYY-MM-DDTHH:MM:SS.ssssss+00:00' ISO-8601 format with microsecond precision, and a timezone offset (+00:00 for UTC)
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss' ISO-8601 format with nanosecond precision
string
Timestamp_ns type values follow the 'YYYY-MM-DDTHH:MM:SS.sssssssss+00:00' ISO-8601 format with nanosecond precision, and a timezone offset (+00:00 for UTC)
string
Fixed length type values are stored and serialized as an uppercase hexadecimal string preserving the fixed length
string
Binary type values are stored and serialized as an uppercase hexadecimal string
string
This optional field is DEPRECATED for REMOVAL since it more safe to handle this internally, and shouldn't be exposed to the clients. The highest assigned column ID for the table. This is used to ensure columns are always assigned an unused ID when evolving schemas. When omitted, it will be computed on the server side.
Schema ID to set as current, or -1 to set last added schema
spec
object
required
fields
object[]
required
Partition spec ID to set as the default, or -1 to set last added spec
sort-order
object
required
fields
object[]
required
Possible values: [asc, desc]
Possible values: [nulls-first, nulls-last]
Sort order ID to set as the default, or -1 to set last added sort order
snapshot
object
required
Location of the snapshot's manifest list file
The first _row_id assigned to the first row in the first data file in the first manifest
The upper bound of the number of rows with assigned row IDs
summary
object
required
Possible values: [append, replace, overwrite, delete]
Possible values: [tag, branch]
updates
object
required
view-version
object
required
Schema ID to set as current, or -1 to set last added schema
summary
object
required
representations
object[]
required
oneOf
Reference to one or more levels of a namespace
circular(SetCurrentViewVersionUpdate)
This optional field is DEPRECATED for REMOVAL since it contains redundant information. Clients should use the statistics.snapshot-id field instead.
statistics
object
required
blob-metadata
object[]
required
properties
object
partition-statistics
object
required
encryption-key
object
required
properties
object
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 419
- 500
- 502
- 503
- 504
- 5XX
View metadata result when loading a view
- application/json
- Schema
- Example (from schema)
Schema
Array [
Array [
- SQLViewRepresentation
]
]
Array [
]
metadata
object
required
Possible values: >= 1 and <= 1
versions
object[]
required
Schema ID to set as current, or -1 to set last added schema
summary
object
required
representations
object[]
required
oneOf
Reference to one or more levels of a namespace
version-log
object[]
required
properties
object
config
object
{
"metadata-location": "string",
"metadata": {
"view-uuid": "string",
"format-version": 0,
"location": "string",
"current-version-id": 0,
"versions": [
{
"version-id": 0,
"timestamp-ms": 0,
"schema-id": 0,
"summary": {},
"representations": [
{}
],
"default-catalog": "string",
"default-namespace": [
"accounting",
"tax"
]
}
],
"version-log": [
{
"version-id": 0,
"timestamp-ms": 0
}
],
"schemas": [
{
"type": "string",
"fields": [
{
"id": 0,
"name": "string",
"type": [
"long",
"string",
"fixed[16]",
"decimal(10,2)"
],
"required": true,
"doc": "string",
"initial-default": true,
"write-default": true
}
],
"schema-id": 0,
"identifier-field-ids": [
0
]
}
],
"properties": {}
},
"config": {}
}
Indicates a bad request error. It could be caused by an unexpected request body format or other forms of request validation failure, such as invalid json. Usually serves application/json content, although in some cases simple text/plain content might be returned by the server's middleware.
- application/json
- Schema
- Example (from schema)
- Example
Schema
error
object
required
JSON error payload returned in a response with further details on the error
Human-readable error message
Internal type definition of the error
Possible values: >= 400 and <= 600
HTTP response code
{
"error": {
"message": "The server does not support this operation",
"type": "UnsupportedOperationException",
"code": 406
}
}
{
"error": {
"message": "Malformed request",
"type": "BadRequestException",
"code": 400
}
}
Unauthorized. The REST Catalog SHOULD respond with the 401 UnauthorizedResponse when the access token provided is expired, revoked, malformed, or invalid for other reasons. The client MAY request a new access token and retry the request.
- application/json
- Schema
- Example (from schema)
- Example
Schema
error
object
required
JSON error payload returned in a response with further details on the error
Human-readable error message
Internal type definition of the error
Possible values: >= 400 and <= 600
HTTP response code
{
"error": {
"message": "The server does not support this operation",
"type": "UnsupportedOperationException",
"code": 406
}
}
{
"error": {
"message": "Not authorized to make this request",
"type": "NotAuthorizedException",
"code": 401
}
}
Forbidden. Authenticated user does not have the necessary permissions.
- application/json
- Schema
- Example (from schema)
- Example
Schema
error
object
required
JSON error payload returned in a response with further details on the error
Human-readable error message
Internal type definition of the error
Possible values: >= 400 and <= 600
HTTP response code
{
"error": {
"message": "The server does not support this operation",
"type": "UnsupportedOperationException",
"code": 406
}
}
{
"error": {
"message": "Not authorized to make this request",
"type": "NotAuthorizedException",
"code": 403
}
}
Not Found - NoSuchViewException, view to load does not exist
- application/json
- Schema
- Example (from schema)
- ViewToUpdateDoesNotExist
Schema
Human-readable error message
Internal type definition of the error
Possible values: >= 400 and <= 600
HTTP response code
{
"message": "string",
"type": "NoSuchNamespaceException",
"code": 404,
"stack": [
"string"
]
}
The requested view does not exist
{
"error": {
"message": "The given view does not exist",
"type": "NoSuchViewException",
"code": 404
}
}
Conflict - CommitFailedException. The client may retry.
- application/json
- Schema
- Example (from schema)
Schema
Human-readable error message
Internal type definition of the error
Possible values: >= 400 and <= 600
HTTP response code
{
"message": "string",
"type": "NoSuchNamespaceException",
"code": 404,
"stack": [
"string"
]
}
This is an optional status response type that the REST Catalog can issue when the token has expired. The client MAY request a new access token and retry the request. 401 UnauthorizedResponse SHOULD be preferred over this response type on token expiry.
- application/json
- Schema
- Example (from schema)
- Example
Schema
error
object
required
JSON error payload returned in a response with further details on the error
Human-readable error message
Internal type definition of the error
Possible values: >= 400 and <= 600
HTTP response code
{
"error": {
"message": "The server does not support this operation",
"type": "UnsupportedOperationException",
"code": 406
}
}
{
"error": {
"message": "Credentials have timed out",
"type": "AuthenticationTimeoutException",
"code": 419
}
}
An unknown server-side problem occurred; the commit state is unknown.
- application/json
- Schema
- Example (from schema)
- Example
Schema
Human-readable error message
Internal type definition of the error
Possible values: >= 400 and <= 600
HTTP response code
{
"message": "string",
"type": "NoSuchNamespaceException",
"code": 404,
"stack": [
"string"
]
}
{
"error": {
"message": "Internal Server Error",
"type": "CommitStateUnknownException",
"code": 500
}
}
A gateway or proxy received an invalid response from the upstream server; the commit state is unknown.
- application/json
- Schema
- Example (from schema)
- Example
Schema
Human-readable error message
Internal type definition of the error
Possible values: >= 400 and <= 600
HTTP response code
{
"message": "string",
"type": "NoSuchNamespaceException",
"code": 404,
"stack": [
"string"
]
}
{
"error": {
"message": "Invalid response from the upstream server",
"type": "CommitStateUnknownException",
"code": 502
}
}
The service is not ready to handle the request, request could have been partially processed. The service may additionally send a Retry-After header to indicate when to retry, a non idempotent request should only be retried by the client when the Retry-After header is present.
- application/json
- Schema
- Example (from schema)
- Example
Schema
error
object
required
JSON error payload returned in a response with further details on the error
Human-readable error message
Internal type definition of the error
Possible values: >= 400 and <= 600
HTTP response code
{
"error": {
"message": "The server does not support this operation",
"type": "UnsupportedOperationException",
"code": 406
}
}
{
"error": {
"message": "Slow down",
"type": "SlowDownException",
"code": 503
}
}
A server-side gateway timeout occurred; the commit state is unknown.
- application/json
- Schema
- Example (from schema)
- Example
Schema
Human-readable error message
Internal type definition of the error
Possible values: >= 400 and <= 600
HTTP response code
{
"message": "string",
"type": "NoSuchNamespaceException",
"code": 404,
"stack": [
"string"
]
}
{
"error": {
"message": "Gateway timed out during commit",
"type": "CommitStateUnknownException",
"code": 504
}
}
A server-side problem that might not be addressable on the client.
- application/json
- Schema
- Example (from schema)
- Example
Schema
Human-readable error message
Internal type definition of the error
Possible values: >= 400 and <= 600
HTTP response code
{
"message": "string",
"type": "NoSuchNamespaceException",
"code": 404,
"stack": [
"string"
]
}
{
"error": {
"message": "Bad Gateway",
"type": "InternalServerError",
"code": 502
}
}