Upsolver Managed Tables

Upsolver tables always exist in a metastore that holds the metadata, allowing you to query them while the underlying files for the table data are stored in a corresponding storage location.

When you have a lakehouse powered by Apache Iceberg, the metadata for your tables is created in the Iceberg layer that sits over your cloud object store; your catalog, such as AWS Glue Data Catalog, then has a pointer to Iceberg to discover the tables.

Apache Iceberg tables can be managed by executing SQL commands that enable you to:

• Write data into a table from an external source.

• Query data from a table.

• Delete data from a table.

• Read data from one table and write it to a different table, either internally or externally.

Upsolver managed Iceberg tables can be created with or without columns. Unlike database tables, Upsolver tables support dynamic column lists, meaning the list of columns can expand based on the data being loaded.

Additionally, when you create the table, you can define primary keys, partition columns, data retention, and more. However, if you plan to run an ingestion job to write to the table, do not specify any primary keys.

Table commands

• CREATE ICEBERG TABLE

• ALTER ICEBERG TABLE

• DROP ICEBERG TABLE