Skip to content

copy to partitioned parquet files saves partition column name in file #118

@shashideore

Description

@shashideore

What happens?

facing this issue with duckdb version 1.4.1
when we run copy table to partitioned parquet with WRITE_PARTITION_COLUMNS false, partition column is still saved in parquet file.

COPY (
SELECT * FROM my_table
)
TO 's3://my-bucket/my_table/'
( FORMAT PARQUET,
PARTITION_BY (GENDER),
WRITE_PARTITION_COLUMNS FALSE,
COMPRESSION snappy
)

To Reproduce

as per duckdb/duckdb#12147 this seem to be resolved but we can see happening.
Can you help resolve ?

OS:

MACOS Version 26.0.1

DuckDB Package Version:

1.4.1

Python Version:

3.12

Full Name:

Shashikant Deore

Affiliation:

SAS

What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.

I have not tested with any build

Did you include all relevant data sets for reproducing the issue?

Yes

Did you include all code required to reproduce the issue?

  • Yes, I have

Did you include all relevant configuration to reproduce the issue?

  • Yes, I have

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions