Standing up an Iceberg + Nessie catalog is now zero-config and works on non-AWS and air-gapped object storage straight away. Ilum sets up the catalog for you and handles its storage credentials automatically. A built-in Nessie catalog just works on any S3-compatible store and under any catalog name, with no Spark settings to edit by hand.
Catalog set up for you: Ilum configures the Iceberg+Nessie catalog from your settings. Choosing a custom catalog name no longer leaves you with a broken catalog.
Credentials handled automatically: the catalog's storage credentials are applied for you and are never stored in or shown by Ilum.
Works off-AWS: the catalog's region is now set correctly, fixing the error that used to hit the very first table creation against non-AWS storage.
Iceberg-on-Nessie used to need careful, easily-broken setup that failed silently on the first write outside AWS. Now it's a default that works the first time, consistently, wherever your object storage lives. Where to find it: create or edit a Nessie catalog from the Metastores view. The region field is right there in the form. Nessie catalog creation Links:Nessie catalog Available in version: 6.7.2
The SQL Editor has received a major UI/UX overhaul, making it faster to navigate multi-query workflows and easier to move between engines without rewriting SQL.
Tab management
You can now open multiple queries and notebooks as tabs across the top of the editor. Switch between active work, reference queries, and tutorials without losing your place. The left sidebar organizes all saved queries by engine, so you can search, browse, and open anything in one click.
SQL Translate: convert between engines instantly
This is the big one. Hit Translate and Ilum will convert your SQL from one dialect to another, across all three supported engines: DuckDB, Trino, and Spark SQL. Moving a quick prototype from DuckDB to a production Spark job? Translate handles the syntax differences so you don't have to. It works in every direction: DuckDB → Spark, Trino → DuckDB, Spark → Trino, and so on.
What else is new in the editor
Format - auto-format your SQL for readability with one click.
Explain - view the query execution plan before running, useful for catching expensive operations early.
Engine picker - switch between DuckDB, Trino, and Spark SQL per query tab. Different tabs can target different engines simultaneously.
Inline results - query output appears directly below the editor with row counts, execution time, and an Export option. Multiple result sets are tabbed so you can compare runs side by side.
Why it matters
Teams working across engines no longer need to context-switch between tools or manually translate SQL dialects. Write exploratory queries in DuckDB for speed, translate to Spark SQL when the workload scales, and keep everything in one place, same editor, same catalog, same lineage.
Powered by FeedBear