[HIVE-2913] BlockMergeTask Doesn't Honor Job Configuration Properties when used directly

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.8.1
• Fix Version/s: 0.9.0
• Component/s: Query Processor
• Hadoop Flags: Reviewed
• Assignee: Thiruvel Thirumoolan
• Reporter: Thiruvel Thirumoolan
• Created: 30/Mar/12 09:38
• Updated: 09/Jan/13 10:24
• Resolved: 03/Apr/12 10:48

Description

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.