We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
COPY
PARTITION_BY
When running:
import duckdb input = duckdb.sql('SELECT year(time) as year, month(time) as month FROM "updates.parquet"') duckdb.sql('''COPY input TO 'output' (FORMAT PARQUET, COMPRESSION ZSTD, PARTITION_BY (year, month), OVERWRITE_OR_IGNORE 1)''')
Results in:
duckdb.duckdb.IOException: IO Error: Could not create directory: 'output\year=2023'
It is difficult to reproduce with static data and seems to only happen with a specific input.
It only happens if the directory has not previously been created.
Saving the input variable into a new parquet file, and then using it as the source of COPY does not trigger the error.
input
Windows
0.9.1
Python
Colin Breame
Statkraft Germany GmbH
main
I have tested with a main build
The text was updated successfully, but these errors were encountered:
65103b0
Merge pull request #9473 from Mytherin/issue9360
182b824
Fix #9360, fix #9466: grab a lock before creating directories to fix race condition on Windows in partitioned write
Successfully merging a pull request may close this issue.
What happens?
When running:
Results in:
To Reproduce
It is difficult to reproduce with static data and seems to only happen with a specific input.
It only happens if the directory has not previously been created.
Saving the
input
variable into a new parquet file, and then using it as the source ofCOPY
does not trigger the error.OS:
Windows
DuckDB Version:
0.9.1
DuckDB Client:
Python
Full Name:
Colin Breame
Affiliation:
Statkraft Germany GmbH
Have you tried this on the latest
main
branch?I have tested with a main build
Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?
The text was updated successfully, but these errors were encountered: