Feature: Implicitly generate null value column when using COPY
#4305
Labels
feature
New features or missing components of existing features
COPY
#4305
API
Other
Description
I have this scenario where I have a CSV/Parquet file with just two columns:
In my DDL, I want to add a nullable column
historical_price
as follows:I want to initialize the node table with all values in the
historical_sales
columns as nulls, and add them viaMERGE
at a later time when they become available.Issue
Because my input file has just 2 columns, and my DDL specifies 3 columns, I cannot use
COPY Product FROM 'product.parquet'
directly.I instead have to do this:
Feature request
In the
COPY
pipeline, because we already know the number of columns in the input prior to importing the data, can we implicitly infer the column names so that we can use the much simpler DDL command below? It would reduce the mental burden on the user, as it's expected that the columns that are absent in the input file would have to be filled with nulls.@ray6080 I think this seems like a reasonable feature, but if you think it's infeasible, feel free to close.
The text was updated successfully, but these errors were encountered: