[
https://issues.apache.org/jira/browse/IGNITE-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584241#comment-17584241
]
Taras Ledkov edited comment on IGNITE-12852 at 8/24/22 1:11 PM:
----------------------------------------------------------------
[~antkr]
1. I guess this patch could me merged because it fixes significant
functionality for users.
2. Agreed. I guess we can introduce one or more parse option to tune parser
behavior. However, checking that the number of fields in the rows is the same
looks good.
was (Author: tledkov):
@[~antkr]
1. I guess this patch could me merged because it fixes significant
functionality for users.
2. Agreed. I guess we can introduce one or more parse option to tune parser
behavior. However, checking that the number of fields in the rows is the same
looks good.
> Comma in field is not supported by COPY command
> -----------------------------------------------
>
> Key: IGNITE-12852
> URL: https://issues.apache.org/jira/browse/IGNITE-12852
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.8
> Reporter: YuJue Li
> Assignee: Anton Kurbanov
> Priority: Critical
> Fix For: 2.14
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> CREATE TABLE test(a int,b varchar(100),c int,PRIMARY key(a));
>
> a.csv:
> 1,"a,b",2
>
> COPY FROM '/data/a.csv' INTO test (a,b,c) FORMAT CSV;
>
> The copy command fails because there is a comma in the second field,but this
> is a fully legal and compliant CSV format
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
