You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Ian Maxon (Jira)" <ji...@apache.org> on 2024/06/14 17:11:00 UTC
[jira] [Updated] (ASTERIXDB-3429) Allow configurable escape character for delimited text parser
[ https://issues.apache.org/jira/browse/ASTERIXDB-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Maxon updated ASTERIXDB-3429:
---------------------------------
Labels: triaged (was: )
> Allow configurable escape character for delimited text parser
> -------------------------------------------------------------
>
> Key: ASTERIXDB-3429
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3429
> Project: Apache AsterixDB
> Issue Type: Improvement
> Components: EXT - External data
> Reporter: Ian Maxon
> Assignee: Ian Maxon
> Priority: Major
> Labels: triaged
> Fix For: 0.9.10
>
>
> The current CSV/Delimited Text parser supports RFC4180-style escaping rules. In brief, this means that string fields can be escaped by surrounding them in " , and " itself can be escaped as "" .
> However, many CSV files do not follow this convention. For example, this row using C-style escaping of quotes would be invalid following RFC4180:
>
> {code:java}
> 1,"The \"quick\" fox, jumped over the lazy dog "{code}
> The CSV parser should allow the escape character to be configurable, to allow parsing of these nonstandard, but common examples.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)