Mailing-List: contact dev-help@pig.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@pig.apache.org
Date: Fri, 1 Mar 2013 14:57:13 +0000 (UTC)
From: "Jonathan Packer (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Message-ID: <JIRA.12629579.1359405478803.364792.1362149833412@arcas>
In-Reply-To: <JIRA.12629579.1359405478803@arcas>
References: <JIRA.12629579.1359405478803@arcas>
Subject: [jira] [Commented] (PIG-3141) Giving CSVExcelStorage an option to
 handle header rows
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/PIG-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590592#comment-13590592 ] 

Jonathan Packer commented on PIG-3141:
--------------------------------------

Hi, I put it on reviewboard here: https://reviews.apache.org/r/9697/ . Sorry, I hadn't known what that was earlier.
                
> Giving CSVExcelStorage an option to handle header rows
> ------------------------------------------------------
>
>                 Key: PIG-3141
>                 URL: https://issues.apache.org/jira/browse/PIG-3141
>             Project: Pig
>          Issue Type: Improvement
>          Components: piggybank
>    Affects Versions: 0.11
>            Reporter: Jonathan Packer
>            Assignee: Jonathan Packer
>             Fix For: 0.12
>
>         Attachments: csv.patch, csv_updated.patch, PIG-3141_update_3.diff
>
>
> Adds an argument to CSVExcelStorage to skip the header row when loading. This works properly with multiple small files each with a header being combined into one split, or a large file with a single header being split into multiple splits.
> Also fixes a few bugs with CSVExcelStorage, including PIG-2470 and a bug involving quoted fields at the end of a line not escaping properly.
> Removes the choice of delimiter, since a CSV file ought to only use a comma delimiter, hence the name.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira