hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joydeep Sen Sarma (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-1463) hive output file names are unnecessarily large
Date Mon, 19 Jul 2010 18:59:51 GMT

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

Joydeep Sen Sarma commented on HIVE-1463:
-----------------------------------------

if u look at the testFileSinkOperator in trunk - it's useless. it doesn't test FileSinkOperator
at all. I noted down in the comments - hive-405 took out the test for filesinkoperator. without
that - the test is just testing the select operator - and this is tested elsewhere in the
same file anyway.

so i took out the old code and left a comment that this test needs to be enhanced to cover
FileSinkOperator more comprehensively in the future.

> 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: 1463.2.patch, 1463.3.patch, hive-1463.1.patch, hive-1463.4.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.


Mime
View raw message