Skip to content
New issue

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

Regression: Can no longer use FORMAT PARQUET in COPY command #9713

Closed
alamb opened this issue Mar 20, 2024 · 1 comment · Fixed by #9744
Closed

Regression: Can no longer use FORMAT PARQUET in COPY command #9713

alamb opened this issue Mar 20, 2024 · 1 comment · Fixed by #9744
Assignees

Comments

@alamb
Copy link
Contributor

alamb commented Mar 20, 2024

Describe the bug

#9604 from @metesynnada rationalized the COPY syntax to match CREATE EXTERNAL TABLE syntax. For example

- COPY (SELECT * FROM 'hits.parquet' LIMIT 10) TO 'clickbench_hits_10.parquet' (FORMAT PARQUET);
+ COPY (SELECT * FROM 'hits.parquet' LIMIT 10) TO 'clickbench_hits_10.parquet' STORED AS PARQUET;

However, this also means the syntax is no longer compatible with duckdb

To Reproduce

❯ COPY (select * from (values (1))) to '/tmp/foo.parquet' OPTIONS (format parquet);
Invalid or Unsupported Configuration: could not find config namespace for key "format"```

Expected behavior

I would like to support the former syntax as well as the new one

So both

❯ COPY (select * from (values (1))) to '/tmp/foo.parquet' OPTIONS (format parquet);
Invalid or Unsupported Configuration: could not find config namespace for key "format"```

And 

```sql
❯ COPY (select * from (values (1))) to '/tmp/foo.parquet' STORED AS PARQUET;
+-------+
| count |
+-------+
| 1     |
+-------+

would work

Additional context

No response

@alamb alamb added bug Something isn't working and removed bug Something isn't working labels Mar 20, 2024
@alamb alamb changed the title Regression: Can no longer Regression: Can no longer use FORMAT PARQUET in COPY command Mar 20, 2024
@tinfoil-knight
Copy link
Contributor

tinfoil-knight commented Mar 22, 2024

take


Waiting for #9723 to be merged to start working on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants