> > How would that look like? We wanted to introduce this logical type to > Parquet specifically, so that table formats such as Delta and Iceberg can > have a simpler protocol change, and that we could provide this as a > consistent format across multiple data processing engines.
I don't think Parquet has to be the de-facto common ground for Iceberg and Delta. I think contributors to the projects should be collaborating directly. Variant made sense in parquet because it has a common use-case regardless of table-format. The File logical type feels like it is a more borderline case, as managing the external file references falls to table format or some higher level coordinator. I like the idea of this being a test case for driving extension types forward. Cheers, Micah On Thu, Apr 9, 2026 at 9:14 AM Antoine Pitrou <[email protected]> wrote: > > Hi Burak, > > Le 08/04/2026 à 20:32, Burak Yavuz a écrit : > > > > @Antoine > >> I feel like this is the kind of use case where a hypothetical extension > > type mechanism would be a better fit than hardcoding dedicated logical > > types in the Thrift definition. > > > > How would that look like? We wanted to introduce this logical type to > > Parquet specifically, so that table formats such as Delta and Iceberg can > > have a simpler protocol change, and that we could provide this as a > > consistent format across multiple data processing engines. > > Some initial discussion took place in > https://github.com/apache/parquet-format/pull/451 > > (also dev ML message: > https://lists.apache.org/thread/tfd8hmfhl69rmml9wq97pr77y3h61zxg) > > But it would need someone motivated to push through. > > Regards > > Antoine. > > >
