[
https://issues.apache.org/jira/browse/HIVE-12820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096829#comment-15096829
]
Aihua Xu commented on HIVE-12820:
---------------------------------
Seems the patch doesn't solve incompatibility issue, e.g., for the case of
"using \r as one separator". Before HIVE-11785, it would escape \r in text into
\\\r (\ and carriage return); with HIVE-11785 it will be "\r" (character \ and
r). If a MR job is involved, the first scenario would return incorrect result
and the second will work.
I'm wondering if we need to make such case compatible as well.
> Remove the check if carriage return and new line are used for separator or
> escape character
> -------------------------------------------------------------------------------------------
>
> Key: HIVE-12820
> URL: https://issues.apache.org/jira/browse/HIVE-12820
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
> Affects Versions: 2.0.0, 2.1.0
> Reporter: Aihua Xu
> Assignee: Aihua Xu
> Attachments: HIVE-12820.2.patch, HIVE-12820.patch
>
>
> The change in HIVE-11785 doesn't allow \r or \n to be used as separator or
> escape character which may break some existing tables which uses \r as
> separator or escape character e.g..
> This case actually can be supported regardless of SERIALIZATION_ESCAPE_CRLF
> set or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
