[
https://issues.apache.org/jira/browse/NIFI-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16163197#comment-16163197
]
ASF GitHub Bot commented on NIFI-4242:
--------------------------------------
Github user Wesley-Lawrence commented on the issue:
https://github.com/apache/nifi/pull/2088
@markap14 Alright, should be all fixed up now. I made sure to test out a
live Flow this time, and make sure the functionality worked outside of just
unit tests.
> CSVReader shouldn't require that an escape character be defined
> ---------------------------------------------------------------
>
> Key: NIFI-4242
> URL: https://issues.apache.org/jira/browse/NIFI-4242
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.3.0
> Reporter: Wesley L Lawrence
> Priority: Minor
> Attachments: NIFI-4242.patch, NIFI-4242.patch
>
>
> There are situations where, when parsing a CSV file, one doesn't want to
> define an escape character. For example, when using quote character ", the
> following is valid CSV;
> {code}
> a,"""b",c
> {code}
> The second column should be interpreted as "b. But when Apache Commons CSV is
> told that there's an escape character, the above row is invalid
> (interestingly, if it was """b""", it would be valid as "b").
> There are known formats that Apache Commons CSV provides, that doesn't define
> escape characters either.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
