You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Mithun Radhakrishnan (JIRA)" <ji...@apache.org> on 2014/02/28 07:49:19 UTC

[jira] [Updated] (OOZIE-1720) Oozie Hive action doesn't honour mapred.job.name.

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

Mithun Radhakrishnan updated OOZIE-1720:
----------------------------------------

    Attachment: OOZIE-1720.patch

The fix. Reset mapred.job.name only if the Oozie default job-name has been set.

> Oozie Hive action doesn't honour mapred.job.name.
> -------------------------------------------------
>
>                 Key: OOZIE-1720
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1720
>             Project: Oozie
>          Issue Type: Bug
>          Components: action
>    Affects Versions: 4.0.0
>            Reporter: Mithun Radhakrishnan
>         Attachments: OOZIE-1720.patch
>
>
> If mapred.job.name is set in the configuration parameters of a Hive Action, one sees that the setting doesn't stick. The Hive job runs with the default hive job-name (i.e. the query, truncated to a certain length). This behaviour prevents users from being able to choose custom job-names for Hive-jobs launched from Oozie workflows.
> The Hive configuration indicates that mapred.job.name (and mapreduce.job.name) are passed into Hive as empty ("").



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)