Skip to content

Column name checks are too strict #39

@onderkalaci

Description

@onderkalaci

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    api-changeincludes breaking changesenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions