hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sushanth Sowmyan (JIRA)" <>
Subject [jira] [Updated] (HIVE-5504) OrcOutputFormat honors compression properties only from within hive
Date Thu, 13 Feb 2014 21:32:21 GMT


Sushanth Sowmyan updated HIVE-5504:

    Release Note: 
Allows OrcOutputFormat.createRecordWriter() to use its table property parameters (like "orc.compress")
if specified in JobConf as well. This codepath is not called from Hive, but will be helpful
to those that want to use OrcOutputFormat as a generic M/R OutputFormat.

In addition, makes changes to HCatalog to look for certain Orc table properties, and if present,
copies them out to JobConf before instantiating OrcOutputFormat, thus passing the properties
back to it. This allows users of Orc from outside Hive to have Orc behave as the metadata
          Status: Patch Available  (was: Open)

> OrcOutputFormat honors  compression  properties only from within hive
> ---------------------------------------------------------------------
>                 Key: HIVE-5504
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: HCatalog
>    Affects Versions: 0.12.0, 0.11.0
>            Reporter: Venkat Ranganathan
>            Assignee: Sushanth Sowmyan
>         Attachments: HIVE-5504.patch
> When we import data into a HCatalog table created with the following storage  description
> .. stored as orc tblproperties ("orc.compress"="SNAPPY") 
> the resultant orc file still uses the default zlib compression
> It looks like HCatOutputFormat is ignoring the tblproperties specified.   show tblproperties
shows that the table indeed has the properties properly saved.
> An insert/select into the table has the resulting orc file honor the tbl property.

This message was sent by Atlassian JIRA

View raw message