hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashish Thusoo (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-85) separate compression options for different output types
Date Tue, 02 Dec 2008 23:50:44 GMT

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

Ashish Thusoo commented on HIVE-85:

When I try to apply  the patch I get the following error

patch: **** malformed patch at line 93: \ No newline at end of fil

I think this is because there is some binary data in the patch. Can you upload those separately?


> 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
>         Attachments: hive-85.patch.1, hive-85.patch.2, hive-85.patch.3
> 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
> 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.

View raw message