Search Shortcut cmd + k | ctrl + k
- Documentation
- Specification
- Introduction
- Data Types
- Queries
- Tables
- Overview
- column
- column_mapping
- name_mapping
- column_tag
- data_file
- delete_file
- file_column_stats
- file_partition_value
- files_scheduled_for_deletion
- inlined_data_tables
- metadata
- partition_column
- partition_info
- schema
- schema_versions
- snapshot
- snapshot_changes
- table
- table_column_stats
- table_stats
- tag
- view
- DuckDB Extension
- Introduction
- Usage
- Connecting
- Choosing a Catalog Database
- Choosing Storage
- Snapshots
- Schema Evolution
- Time Travel
- Upserting
- Configuration
- Paths
- Maintenance
- Recommended Maintenance
- Merge Files
- Expire Snapshots
- Cleanup of Files
- Rewrite Files with Deletes
- Checkpoint
- Advanced Features
- Constraints
- Conflict Resolution
- Data Change Feed
- Data Inlining
- Encryption
- Partitioning
- Transactions
- Row Lineage
- Views
- Comments
- Metadata
- Migrations
- Guides
- Unsupported Features
- FAQ
Documentation
/ Specification
/ Tables
ducklake_column_mapping
Mappings contain the information used to map Parquet fields to column ids in the absence of field-id
s in the Parquet file.
Column name | Column type | |
---|---|---|
mapping_id |
BIGINT |
|
table_id |
BIGINT |
|
type |
VARCHAR |
mapping_id
is the numeric identifier of the mapping.mapping_id
is incremented fromnext_catalog_id
in theducklake_snapshot
table.table_id
refers to atable_id
from theducklake_table
table.type
defines what method is used to perform the mapping.
The valid type
values are the following:
type |
Description |
---|---|
map_by_name |
Map the columns based on the names in the Parquet file |