You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (Jira)" <ji...@apache.org> on 2026/01/05 10:41:00 UTC

[jira] [Updated] (NIFI-4242) CSVReader shouldn't require that an escape character be defined

     [ https://issues.apache.org/jira/browse/NIFI-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre Villard updated NIFI-4242:
---------------------------------
    Resolution: Feedback Received
        Status: Resolved  (was: Patch Available)

Apache NiFi 1.x is no longer maintained and no new release is planned on the 1.x release line. Marking as resolved as part of a cleanup operation. Please open a new one with an updated description if this is still relevant for NiFi 2.x.

> 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
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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
(v8.20.10#820010)