[FALCON-204] Process mapper generates params assuming table input and output as names literally

• Type: Sub-task
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.4
• Fix Version/s: 0.4
• Component/s: process
• Assignee: Venkatesh Seetharam
• Reporter: Venkatesh Seetharam
• Due: 15/Nov/13
• Created: 15/Nov/13 20:49
• Updated: 22/Nov/13 09:13
• Resolved: 15/Nov/13 22:34

Description

org.apache.falcon.converter.OozieProcessMapper generates input params assuming input as the name rather than using user provided name which results in coordinator submission failure. Same is true of output as well.

This is true only if input and output are of table storage but not file system.

props.put(prefix + "_partition_filter_pig", "${coord:dataInPartitionFilter('input', 'pig')}");   
props.put(prefix + "_partition_filter_hive", "${coord:dataInPartitionFilter('input', 'hive')}"); 
props.put(prefix + "_partition_filter_java", "${coord:dataInPartitionFilter('input', 'java')}"); 

props.put(prefix + "_dataout_partitions", "${coord:dataOutPartitions('output')}");

Issue Links

• is duplicated by: FALCON-214 Process scheduling fails in oozie