[
https://issues.apache.org/jira/browse/HIVE-12820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15094887#comment-15094887
]
Aihua Xu commented on HIVE-12820:
---------------------------------
Yes. Practically escapeChar can't be \r or \n anyway since when we send the
task to MapReduce, it will break the text based on \n incorrectly even without
such escaping. We should add the check of escapeChar ideally, but I won't try
to address that in here to cause possible incompatibility and lose
functionality. The user can choose not to use that.
> 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)
