Skip to main content
Ryft seamlessly manages your Iceberg lakehouse and ensures it stays in top-notch performance and health. You can enable management at any level — individual tables, namespaces, or entire catalogs — and Ryft will handle maintenance and optimization automatically. Customize settings where needed, and inherit smart defaults everywhere else.

Intelligent Self-Tuning

Ryft continuously adapts to real-time workload patterns, ensuring that table structure and performance remain optimal as data evolves, without manual work. By dynamically adjusting compaction operations and metadata maintenance based on usage patterns, Ryft minimizes performance bottlenecks and maximizes query efficiency.

Customization & Visibility

All management settings are fully customizable, so teams that require fine-tuned adjustments can configure parameters to match specific workload needs. Ryft also provides detailed visibility into management operations, allowing you to monitor the impact on query performance and resource utilization. Table Management

Management Scope

Management can be enabled at three levels, with settings flowing down from broader to narrower scopes:

Catalog

Enabling management at the catalog level applies to all current and future tables in the catalog. This is the simplest way to get started - one action covers your entire catalog.

Namespace

Enabling management at the namespace level applies to all current and future tables in the selected namespace. Namespace-level settings take precedence over catalog-level settings.

Table

You can enable or customize management for a specific table. Table-level settings always take precedence over namespace-level and catalog-level settings.

Example

  • Enable management at the catalog level with automatic settings across the board.
  • Override Snapshot Lifecycle settings for the bronze namespace to use a longer retention window.
  • Override Data Compaction for the bronze.enriched_events table to use a custom sort strategy.
  • Result: bronze.enriched_events uses custom compaction but inherits all other settings from the bronze namespace. The bronze namespace uses custom snapshot lifecycle but inherits everything else from the catalog. All other tables use the catalog defaults.
As seen in the example above, overrides are granular — you can override individual settings while inheriting the rest from the parent scope. You can revert an override by resetting the setting to inherit from the parent.

Management Settings

Each managed scope includes configuration for the following procedures:

Using Managed Tables

Enable management by clicking “Enable Management” on any table, namespace, or catalog page. You can accept the automatic defaults or customize settings before applying. Once enabled, you can manage and monitor your tables through:
  • Management tab — view and configure settings, and track recent runs for any table, namespace, or catalog.
  • Tables tab — available on namespace and catalog pages, showing all tables with their management status.
  • Asset Explorer — filter and sort tables by management status across your entire lakehouse.
Tables Tab