`overwrite` parameter in `to_parquet` does nothing
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
Research direction
Look at the write_parquet method in the Python bindings, likely in a file like src/duckdb_python/relation.py or similar. The overwrite parameter should be passed to the underlying C++ function. Check how other parameters are handled and trace the call to see where overwrite is ignored. Write a test using the provided reproduction script to verify the fix.
Written by the indexing model from the issue text.
Description
What happens?
When using to to_parquet and setting overwrite=False, the file is still overwritten. No warning or exception is raised.
To Reproduce
import duckdb
con = duckdb.connect()
con.sql("SELECT 1 as test").write_parquet("test.parquet")
con.close()
con = duckdb.connect()
con.from_parquet("test.parquet").show()
con.sql("SELECT 2 as test").write_parquet("test.parquet", overwrite=False)
con.from_parquet("test.parquet").show()
OUTPUT
┌───────┐
│ test │
│ int32 │
├───────┤
│ 1 │
└───────┘
┌───────┐
│ test │
│ int32 │
├───────┤
│ 2 │
└───────┘
OS:
macOS Tahoe 26.6.2
DuckDB Package Version:
1.5.5
Python Version:
3.13.15
Full Name:
Luke Strange
Affiliation:
The Data City
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have tested with a stable release
Did you include all relevant data sets for reproducing the issue?
Not applicable - the reproduction does not require a data set
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
- Dominant language
- Python
- Stars
- 186
- Forks
- 113
- Avg merge
- 22h 45m
- Merged PRs (30d)
- 14
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from duckdb/duckdb-python
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
duckdb/duckdb-python#627 ·
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
duckdb/duckdb-python#576 · 3 comments ·
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
duckdb/duckdb-python#534 ·
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
duckdb/duckdb-python#386 ·
-
needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
duckdb/duckdb-python#622 ·
All issues in duckdb/duckdb-python
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stephrobert/dsoxlab#238 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sublimehq/package_control#1780 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nwg-piotr/nwg-displays#145 ·