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

Lefty Leverenz commented on HIVE-5795:
--------------------------------------

When this is committed, we'll need documentation for:

* hive.file.max.footer -- new config parameter
* skip.header.line.count -- serde property for table
* skip.footer.line.count -- serde property for table

The patch documents hive.file.max.footer in hive-default.xml.template, so the 
parameter just needs to be added to the wikidoc.  Note the property names:  not 
skip.xxx.number as shown in this ticket's description but skip.xxx.line.count.

> 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: Bug
>            Reporter: Shuaishuai Nie
>            Assignee: Shuaishuai Nie
>         Attachments: HIVE-5795.1.patch, HIVE-5795.2.patch, HIVE-5795.3.patch, 
> HIVE-5795.4.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.number"="1", 
> "skip.footer.number"="2");
> {code}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to