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.

Sign up for GitHub

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

Jump to bottom

Column name checks are too strict #39

Open

onderkalaci opened this issue Oct 8, 2024 · 0 comments

Labels

onderkalaci commented Oct 8, 2024

I think we should not care much about the column names, we already check the column types, which is fine.

 create table t1(a int);

 insert into t1 VALUES (1);
 copy t1 to '/tmp/data.parquet';

create table t2(b int);
copy t2 from '/tmp/data.parquet';
ERROR:  column "b" is not found in parquet file

onderkalaci added the enhancement label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment