You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Carl Steinbach (JIRA)" <ji...@apache.org> on 2010/07/23 18:50:52 UTC

[jira] Updated: (HIVE-85) separate compression options for different output types

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

Carl Steinbach updated HIVE-85:
-------------------------------

    Fix Version/s: 0.3.0

> separate compression options for different output types
> -------------------------------------------------------
>
>                 Key: HIVE-85
>                 URL: https://issues.apache.org/jira/browse/HIVE-85
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Query Processor
>            Reporter: Joydeep Sen Sarma
>            Assignee: Joydeep Sen Sarma
>             Fix For: 0.3.0
>
>         Attachments: hive-85.patch.1, hive-85.patch.2, hive-85.patch.3, hive-85.patch.4, hive-85.patch.5, lt100.txt.deflate
>
>
> currently hive uses mapred.output.compress to determine compression for all output files. however not all files are final output. at least three different kinds of output files are generated:
> 1. intermediate output files for next map-reduce job
> 2. files targeted for result hdfs directories or hive tables/partitions (which are just hdfs dirs)
> 3. files written to user local directories (downloading results)
> the plan is to provide three separate options for controlling 1,2,3 separately. we may want to split (2) in case compression is determined by table metadata (and not session options).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.