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

["Venkatesh Seetharam (JIRA)" <ji...@apache.org>]

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

Venkatesh Seetharam updated FALCON-204:
---------------------------------------

    Issue Type: Sub-task  (was: Bug)
        Parent: FALCON-192

> Process mapper generates params assuming table input and output as names literally
> ----------------------------------------------------------------------------------
>
>                 Key: FALCON-204
>                 URL: https://issues.apache.org/jira/browse/FALCON-204
>             Project: Falcon
>          Issue Type: Sub-task
>          Components: process
>    Affects Versions: 0.4
>            Reporter: Venkatesh Seetharam
>            Assignee: Venkatesh Seetharam
>            Priority: Blocker
>             Fix For: 0.4
>
>
> 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.
> {code}
> 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')}");
> {code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)