Mailing-List: contact hive-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hive-dev@hadoop.apache.org
Message-ID: <15309684.431191279322152205.JavaMail.jira@thor>
Date: Fri, 16 Jul 2010 19:15:52 -0400 (EDT)
From: "He Yongqiang (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Subject: [jira] Commented: (HIVE-1463) hive output file names are
 unnecessarily large
In-Reply-To: <28538387.362411279061630859.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

He Yongqiang commented on HIVE-1463:
------------------------------------

Agreed with Ning. Need to be especially careful about the renaming to make sure the renaming will not change the ordering of filenames.
Both bucket map join and bucket sort map join just sort the filenames to match buckets in different tables.

> hive output file names are unnecessarily large
> ----------------------------------------------
>
>                 Key: HIVE-1463
>                 URL: https://issues.apache.org/jira/browse/HIVE-1463
>             Project: Hadoop Hive
>          Issue Type: Improvement
>            Reporter: Joydeep Sen Sarma
>         Attachments: hive-1463.1.patch
>
>
> Hive's output files are named like this:
> attempt_201006221843_431854_r_000000_0
> out of all of this goop - only one character '0' would have sufficed. we should fix this. This would help environments with namenode memory constraints.

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