[jira] [Commented] (HIVE-5795) Hive should be able to skip header and footer rows when reading data file for a table

["Sergey Shelukhin (JIRA)" <ji...@apache.org>]

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

Sergey Shelukhin commented on HIVE-5795:
----------------------------------------

This forces the entire input into a single split, which defeats the purpose of using Hive in the first place. I would not recommend anyone to use this feature except for experimentation. The headers/footers should be cleared as part of the ETL process.

> Hive should be able to skip header and footer rows when reading data file for a table
> -------------------------------------------------------------------------------------
>
>                 Key: HIVE-5795
>                 URL: https://issues.apache.org/jira/browse/HIVE-5795
>             Project: Hive
>          Issue Type: New Feature
>            Reporter: Shuaishuai Nie
>            Assignee: Shuaishuai Nie
>              Labels: TODOC13
>             Fix For: 0.13.0
>
>         Attachments: HIVE-5795.1.patch, HIVE-5795.2.patch, HIVE-5795.3.patch, HIVE-5795.4.patch, HIVE-5795.5.patch
>
>
> Hive should be able to skip header and footer lines when reading data file from table. In this way, user don't need to processing data which generated by other application with a header or footer and directly use the file for table operations.
> To implement this, the idea is adding new properties in table descriptions to define the number of lines in header and footer and skip them when reading the record from record reader. An DDL example for creating a table with header and footer should be like this:
> {code}
> Create external table testtable (name string, message string) row format delimited fields terminated by '\t' lines terminated by '\n' location '/testtable' tblproperties ("skip.header.line.count"="1", "skip.footer.line.count"="2");
> {code}



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