In the COPY command, are you specifying the column names?
No, we are not mentioning the column names in the COPY command.
Does it cause an issue?
The extra columns are allowed by design.
Users often need to add new columns to extracts but they may not wish to add those columns to the Redshift table.
For the reverse case, the FILLRECORD parameter allows files with columns missing at the end each row to be loaded.
Can Redshift copy function take partial CDC 'Change data capture' data ? Namely, only primary key(s) and any fields that have changedasked 3 months ago
Copying earlier version of object in S3 bucket to Redshift with COPY commandasked 2 months ago
Failed to COPY parquet files from S3 to Redshiftasked a month ago
Copy command is ignoring extra columns in case of BLANK valuesasked 4 years ago
Copy from S3 parquet to Redshift tableasked 4 years ago
s3 parquet partitions load to redshift using COPY commandasked 2 months ago
Redshift COPY command CPU spikesAccepted Answerasked 5 years ago
COPY ignoring extra columnsasked 6 months ago
Redshift Copy fails due to '\' present in some of the data in my csv fileasked 2 years ago
Redshift COPY commend takes the wrong file from S3asked 3 months ago