[
https://issues.apache.org/jira/browse/HIVE-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phabricator updated HIVE-2913:
------------------------------
Attachment: HIVE-2913.D2547.1.patch
thiruvel requested code review of "HIVE-2913 [jira] BlockMergeTask Doesn't
Honor Job Configuration Properties when used directly".
Reviewers: JIRA
https://issues.apache.org/jira/browse/HIVE-2913
HIVE-2913: Running BlockMergeTask through its main() interface should honor
jobconf properties
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.
TEST PLAN
EMPTY
REVISION DETAIL
https://reviews.facebook.net/D2547
AFFECTED FILES
ql/src/java/org/apache/hadoop/hive/ql/io/rcfile/merge/BlockMergeTask.java
MANAGE HERALD DIFFERENTIAL RULES
https://reviews.facebook.net/herald/view/differential/
WHY DID I GET THIS EMAIL?
https://reviews.facebook.net/herald/transcript/5793/
Tip: use the X-Herald-Rules header to filter Herald messages in your client.
> 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