hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thiruvel Thirumoolan (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-2913) BlockMergeTask Doesn't Honor Job Configuration Properties when used directly
Date Mon, 02 Apr 2012 09:22:19 GMT

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

Thiruvel Thirumoolan updated HIVE-2913:
---------------------------------------

    Status: Patch Available  (was: Open)
    
> BlockMergeTask Doesn't Honor Job Configuration Properties when used directly
> ----------------------------------------------------------------------------
>
>                 Key: HIVE-2913
>                 URL: https://issues.apache.org/jira/browse/HIVE-2913
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Processor
>    Affects Versions: 0.8.1
>            Reporter: Thiruvel Thirumoolan
>            Assignee: Thiruvel Thirumoolan
>            Priority: Minor
>             Fix For: 0.9.0
>
>         Attachments: HIVE-2913.D2547.1.patch, HIVE-2913_1.patch, blockmerge.sh
>
>
> BlockMergeTask has a main() and when used directly (instead of say partition concatenate
feature), the -jobconf arguments are not honored. This is not something most people directly
use.
> Usage:
> BlockMergeTask -input <colon seperated input paths>  -outputDir outputDir [-jobconf
k1=v1 [-jobconf k2=v2] ...] 
> To reproduce:
> Run BlockMergeTask with say -jobconf mapred.job.name=test and launched job will have
a different name.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message