Skip to content

Iceberg Table insert can't handle supplied columns #444

@Tishj

Description

@Tishj

First raised here: https://github.com/duckdblabs/duckdb-internal/issues/5755

require-env ICEBERG_SERVER_AVAILABLE

require avro

require parquet

require iceberg

require httpfs

require aws

# Do not ignore 'HTTP' error messages!
set ignore_error_messages

statement ok
CREATE SECRET local_catalog_secret (
    TYPE S3,
    KEY_ID 'admin',
    SECRET 'password',
    ENDPOINT '127.0.0.1:9000',
    URL_STYLE 'path',
    USE_SSL 0
);

statement ok
ATTACH '' AS my_datalake (
    TYPE ICEBERG,
    CLIENT_ID 'admin',
    CLIENT_SECRET 'password',
    ENDPOINT 'http://127.0.0.1:8181'
);

statement ok
use my_datalake.default;

statement ok
insert into my_datalake.default.empty_table(col2) VALUES (42)

The last statement is the interesting bit, the rest is just boilerplate.
Note the use of my_datalake.default.empty_table(col2)

empty_table is of schema:

empty_table(col1 DATE, col2 INTEGER, col3 VARCHAR)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions