Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Sun, 12 Jun 2016 11:36:21 +0000 (UTC)
From: "Nemon Lou (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.12683861.1386690939000.64384.1465731381139@Atlassian.JIRA>
In-Reply-To: <JIRA.12683861.1386690939000@Atlassian.JIRA>
References: <JIRA.12683861.1386690939000@Atlassian.JIRA> <JIRA.12683861.1386690939282@arcas>
Subject: [jira] [Updated] (HIVE-5999) Allow other characters for LINES
 TERMINATED BY
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 12 Jun 2016 11:36:22 -0000


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

Nemon Lou updated HIVE-5999:
----------------------------
    Status: Open  (was: Patch Available)

> Allow other characters for LINES TERMINATED BY 
> -----------------------------------------------
>
>                 Key: HIVE-5999
>                 URL: https://issues.apache.org/jira/browse/HIVE-5999
>             Project: Hive
>          Issue Type: Improvement
>          Components: Beeline, Database/Schema, Hive
>    Affects Versions: 0.12.0
>            Reporter: Mariano Dominguez
>            Assignee: Nemon Lou
>            Priority: Critical
>              Labels: Delimiter, Hive, Row, SerDe
>         Attachments: HIVE-5999.1.patch, HIVE-5999.patch
>
>
> LINES TERMINATED BY only supports newline '\n' right now.
> It would be nice to loosen this constraint and allow other characters.
> This limitation seems to be hardcoded here:
> https://github.com/apache/hive/blob/trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/BaseSemanticAnalyzer.java#L171
> The DDL Definition on the Hive Language manual shows this as a configurable property whereas it is not. This may lead to mileading assement of being able to choose a choice of field delimiter.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)