Reputation: 41127
I am producing a comma-separated file in S3 that needs to be copied to a staging table in a redshift database using the postgres COPY
command.
It has one boolean
field. With every sensible way I can think of to represent the boolean value in the file, redshift copy complains, usually with "Unknown boolean format".
I'm going to give up and change the staging table field to a smallint
so that I can proceed with the copy and translate the value on the load from staging to the final redshift table, but I'm curious if anyone knows the correct incantation.
Upvotes: 2
Views: 4166
Reputation: 1
Check to make sure you're excluding the headers during the COPY
command.
I ran into the same problem, but adding the ignoreheader 1
option (ignores 1 header line during import) solved the issue.
Upvotes: 0
Reputation: 14035
A zero or one works just fine for us.
Check your loads carefully, it may well be another issue that's 'pushing' invalid data into your boolean column.
For instance, we had all kinds of crazy characters embedded in our data that would cause errors like that. I eventually settled on using the US
character for the record separator.
Upvotes: 1