Parquet Encryption - #9392

I did check locally, and compiles with duckdb-wasm (was unsure about dependencies, and should set a proper CI job to do this). Yey!
Minor data point: DuckDB binary size difference (while bundling parquet, as per the default configuration) is 2%.

Thanks!

Perhaps this is not the right place to ask, but I'm unsure. Can encryption be applied on a column-by-column basis, such that specific information is accessible only with a specific encryption key?
I mean not only the whole file

Maybe attribute based authorization or Attribute-Based Access Control (ABAC)

Hi @Youssef-Harby,

Unfortunately we do not support encryption on a column by column basis yet.
Feel free to take a look at the docs for any other questions! https://duckdb.org/docs/data/parquet/encryption

Hello,

Doing very simple test for .10 version
(Downloaded latest version with winget install DuckDB.cli )

select * from md;
┌────────┐
│ Id │
│ int32 │
├────────┤
│ 0 rows │
└────────┘
insert into md (Id) values (1);
insert into md (Id) values (2);
select * from md;
┌───────┐
│ Id │
│ int32 │
├───────┤
│ 1 │
│ 2 │
└───────┘
PRAGMA add_parquet_key('key256', '01234567891123450123456789112345');
┌─────────┐
│ Success │
│ boolean │
├─────────┤
│ 0 rows │
└─────────┘
COPY md TO 'tbl.parquet' (ENCRYPTION_CONFIG {footer_key: 'key256'});

Error: Invalid Error: Unable to generate random data

Not sure what I'm doing wrong.

@alexandroid11 this works fine for me on macOS:

create table md (id int32);
select * from md;
insert into md (Id) values (1);
insert into md (Id) values (2);
select * from md;
PRAGMA add_parquet_key('key256', '01234567891123450123456789112345');
COPY md TO 'tbl.parquet' (ENCRYPTION_CONFIG {footer_key: 'key256'});

PRAGMA add_parquet_key('key256', '01234567891123450123456789112345');
FROM read_parquet('tbl.parquet', encryption_config = {footer_key: 'key256'});

┌───────┐
│  id   │
│ int32 │
├───────┤
│     1 │
│     2 │
└───────┘

If you can reproduce the issue on a fresh set up, please feel free to open a new issue!