Mailing-List: contact hive-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hive-dev@hadoop.apache.org
Message-ID: <1276521357.1227812444668.JavaMail.jira@brutus>
Date: Thu, 27 Nov 2008 11:00:44 -0800 (PST)
From: "Joydeep Sen Sarma (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Subject: [jira] Assigned: (HIVE-85) separate compression options for
 different output types
In-Reply-To: <1283994070.1227812444631.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Joydeep Sen Sarma reassigned HIVE-85:
-------------------------------------

    Assignee: Joydeep Sen Sarma

> 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
>            Reporter: Joydeep Sen Sarma
>            Assignee: Joydeep Sen Sarma
>
> 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.