hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aihua Xu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-12820) Remove the check if carriage return and new line are used for separator or escape character
Date Mon, 11 Jan 2016 17:15:40 GMT

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

Aihua Xu updated HIVE-12820:
----------------------------
    Description: 
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.

  was:
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..

Seems to make sense to have that check only when SERIALIZATION_ESCAPE_CRLF is set. 


> 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)

Mime
View raw message