Use RFC 4180 Compliant CSV Files for Upload

By default, the COPY command expects delimited data even if the delimiter character is not present inside individual data fields. 

In the RFC 4180 document, the CSV format describes an encoding structure with a delimiter, double quotes, or even newline characters within data fields. 

The following example is a valid CSV file with a header line and a single data record:

product_id,product_name,product_description,product_price
12345,"1"" by 5 Yards Duct Tape","Great choice for your creative projects
Super performance strength
Available in white, red, green and black",9.95

This CSV file looks like the following in a spreadsheet application:

product_id

product_name

product_description

product_price

12345

1" by 5 Yards Duct Tape

Great choice for your creative projects

Super performance strength

Available in white, red, green and black

9.95

To load CSV data with all escaping possibilities defined in RFC 4180, explicitly specify the CSV parser using WITH PARSER GdcCsvParser, which is a GoodData-specific CSV parser in Data Warehouse.

Example:

COPY customers FROM LOCAL 'customers.csv.gz' GZIP WITH PARSER GdcCsvParser

To load CSV data with all escaped characters, as specified in RFC 4180, explicitly specify the CSV parser using the GdcCsvParser, a GoodData-specific parser for Data Warehouse, and include the escape character using ESCAPE AS

COPY customers FROM LOCAL 'customers.csv.gz' GZIP
WITH PARSER GdcCsvParser ESCAPE AS '"'