We're still using parquet. So we use the native duckdb format for intermediate processing (during pipeline execution) but the end results are saved out as parq

We're still using parquet. So we use the native duckdb format for intermediate processing (during pipeline execution) but the end results are saved out as parquet. This is partly because customers often read the data from other tools (e.g. AWS athena) I'd be interested in hearing about experiences of using duckdb files though, i can see instances where it could be useful to us