/AWS1/CL_S3TICEBERGMETADATA¶
Contains details about the metadata for an Iceberg table.
CONSTRUCTOR¶
IMPORTING¶
Optional arguments:¶
io_schema TYPE REF TO /AWS1/CL_S3TICEBERGSCHEMA /AWS1/CL_S3TICEBERGSCHEMA¶
The schema for an Iceberg table. Use this property to define table schemas with primitive types only. For schemas that include nested or complex types such as
struct,list, ormap, useschemaV2instead.
io_schemav2 TYPE REF TO /AWS1/CL_S3TICEBERGSCHEMAV2 /AWS1/CL_S3TICEBERGSCHEMAV2¶
The schema for an Iceberg table using the V2 format. Use this property to define table schemas that include nested or complex data types such as
struct,list, ormap, in addition to primitive types. For schemas with only primitive types, you can use eitherschemaorschemaV2.
io_partitionspec TYPE REF TO /AWS1/CL_S3TICEBERGPARTSPEC /AWS1/CL_S3TICEBERGPARTSPEC¶
The partition specification for the Iceberg table. Partitioning organizes data into separate files based on the values of one or more fields, which can improve query performance by reducing the amount of data scanned. Each partition field applies a transform (such as identity, year, month, or bucket) to a single field.
io_writeorder TYPE REF TO /AWS1/CL_S3TICEBERGSORTORDER /AWS1/CL_S3TICEBERGSORTORDER¶
The sort order for the Iceberg table. Sort order defines how data is sorted within data files, which can improve query performance by enabling more efficient data skipping and filtering.
it_properties TYPE /AWS1/CL_S3TTABLEPROPERTIES_W=>TT_TABLEPROPERTIES TT_TABLEPROPERTIES¶
A map of custom configuration properties for the Iceberg table.
Queryable Attributes¶
schema¶
The schema for an Iceberg table. Use this property to define table schemas with primitive types only. For schemas that include nested or complex types such as
struct,list, ormap, useschemaV2instead.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_SCHEMA() |
Getter for SCHEMA |
schemaV2¶
The schema for an Iceberg table using the V2 format. Use this property to define table schemas that include nested or complex data types such as
struct,list, ormap, in addition to primitive types. For schemas with only primitive types, you can use eitherschemaorschemaV2.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_SCHEMAV2() |
Getter for SCHEMAV2 |
partitionSpec¶
The partition specification for the Iceberg table. Partitioning organizes data into separate files based on the values of one or more fields, which can improve query performance by reducing the amount of data scanned. Each partition field applies a transform (such as identity, year, month, or bucket) to a single field.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_PARTITIONSPEC() |
Getter for PARTITIONSPEC |
writeOrder¶
The sort order for the Iceberg table. Sort order defines how data is sorted within data files, which can improve query performance by enabling more efficient data skipping and filtering.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_WRITEORDER() |
Getter for WRITEORDER |
properties¶
A map of custom configuration properties for the Iceberg table.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_PROPERTIES() |
Getter for PROPERTIES, with configurable default |
ASK_PROPERTIES() |
Getter for PROPERTIES w/ exceptions if field has no value |
HAS_PROPERTIES() |
Determine if PROPERTIES has a value |