The original promise of the data lake was simple: a single, universal home for all an organization’s data. Whether structured database exports, raw text documents, audio recordings, or high-resolution imagery, everything landed in object storage. But as data lakes grew into sprawling swamps lacking transactional guarantees and consistency, the industry pioneered the lakehouse.
Open table formats like Apache Iceberg brought order to the chaos, introducing data warehouse rigor—ACID transactions, snapshot isolation, partition evolution, and fast columnar pruning—directly to cloud storage.
Yet, in our collective rush to build the “house”, we quietly left the “lake” behind.
With the rapid rise of multimodal Large Language Models (LLMs), interest in processing unstructured data directly within the lakehouse has grown rapidly. Multimodal LLMs enable modern data warehouses and lakehouses to analyze unstructured inputs—such as raw images, audio, and documents—much like traditional structured data, without requiring complex, bespoke machine learning staging pipelines.
Because table formats were designed around structured rows and columns, unstructured media was left behind. Raw files were relegated back to external storage buckets, loosely connected to analytical tables through plain, unvalidated string URIs.
The Apache Iceberg community recently took a major step toward reuniting these two worlds by merging support for the new FILE data type into the Iceberg specification.
Limitations of using bare string URIs
Historically, platforms referenced external unstructured assets by storing simple string paths inside tabular columns. While straightforward, relying on plain string URIs introduces several operational challenges:
- No file metadata in the table: A string path doesn't say what type a file is or how big it is. Engines guess types from file extensions, or make a separate call to object storage for each file.
- Inconsistent engine behavior: Nothing marks a string column as a file reference, so every engine and team invents its own way of handling one, and what one writes, another can't reliably interpret.
- No way to detect changes: If a file is replaced at the same path, the string stays the same, so nothing in the table shows that the bytes behind it have changed.
Addressing these operational bottlenecks required a structural shift in how table formats model unstructured assets.
Introducing the FILE type
In the specification slated for Iceberg v4, FILE is defined as a specialized nested type. Rather than treating external assets as opaque strings, it bundles the essential dimensional, transport, and integrity properties of unstructured data into a single schema element:
The native FILE type resolves these operational bottlenecks by storing essential file metadata alongside the reference in every value. Instead of storing an opaque path string, the column stores a structured reference containing standard attributes like uri, offset, size, content_type, checksum, and inline payload. Standardizing these properties gives query engines a single, predictable contract to handle common file management challenges:
- Pay metadata fetch costs once: Writers capture file metadata such as size and content type once, in a standard format that any engine supporting the
FILEtype can read. Engines no longer have to make a separate call to object storage for each file every time they plan a query. - Detect stale metadata with checksums: Storing typed digests or ETags as
checksumexplicitly allows readers to detect when underlying files are modified or out of date, preventing silent asset drift. - Supply required metadata for LLM processing: The
content_typeattribute delivers explicit MIME metadata directly to multimodal LLMs and inference APIs, eliminating reliance on fragile file extension guessing. - Embedded micro-asset storage: Small binary payloads can be stored directly inside the
inlinefield. The resolution rule allows engines to stream these co-located locally during columnar scans, bypassing the need to store an additional object entirely. - Govern structured and unstructured data side by side: The primary win lies in bringing structured business attributes and raw media assets into the exact same transactional table snapshot under unified governance.
Now that we know how and why the FILE type is structured as such, let’s take a look at it in action.
The FILE type in action: Native multimodal AI
Historically, tables pointed at unstructured files with plain string paths. Everything an engine needed to know about a file (what type it is, how big it is, whether it has changed) lived somewhere else: inside tables each team designed for itself, or only in object storage. Let’s look at an example where this breaks down. A claims application keeps policy data in the lakehouse, photos and documents in object storage, and file details in a side table that one team built and others had to find and join by path.
When multimodal AI processing happens (reading the bytes, calling a model, writing results back) the process breaks because of everything around it. Every engine has to guess file types from extensions, track down someone else's side table, or call object storage once per file. And when a file is replaced at the same path, nothing in the table changed, so nobody could tell.
Consider an auto insurer that uses this structure. Each claim pairs structured data (policy, amount, status, and the customer's written account of the accident) with evidence files: damage photos, repair-estimate PDFs, and recorded phone statements. They want to answer this question: "Which open claims have videos that aren’t zero bytes, and has any of that evidence changed since an adjuster reviewed it?"
Finding the videos becomes a filter on real metadata:
Consider how this simplifies an end-to-end multimodal workflow:
- Every engine reads the same column: Teams using different engines can read the same data.
- Filter on the real type: The job filters on
content_typeinstead of guessing from extensions, and statistics lets engines skip data files that contain no data. - Changed evidence gets flagged: Comparing the checksum recorded at intake with the current object shows when a photo has been replaced.
- Go straight to the bytes: Engines read the exact byte range from
uri,offset, andsize, and passcontent_typeto the multimodal model, with no side table and no extra metadata calls.
By elevating files from unmanaged external pointers to governed schema types, Iceberg transforms multimodal AI from a brittle multi-system coordination problem into a standard analytical query.
Ecosystem impact and looking ahead
The integration of the FILE type into the Apache Iceberg specification marks a major step forward for open lakehouse architectures. Rather than forcing organizations to rely on proprietary wrappers or fragmented storage systems to handle unstructured media, Iceberg establishes a portable, open standard.
With the specification finalized and targeted for adoption in the upcoming Iceberg v4 release, momentum now turns to native reader and writer implementations across the open source compute ecosystem—including Apache Spark, Trino, and DuckDB. As multimodal AI becomes an integral part of everyday enterprise workflows, standardizing the FILE type ensures that the open lakehouse remains the definitive, vendor-neutral foundation for structured and unstructured data alike.