[
https://issues.apache.org/jira/browse/OOZIE-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-1387:
---------------------------------
Attachment: OOZIE-1387.patch
The patch makes it so that it will accept either
{{mapred.mapper/reducer.class}} or {{mapreduce.map/reduce.class}} with
{{mapred.mapper/reducer.class}} having priority.
New unit test verifies that it accepts {{mapreduce.map/reduce.class}} and I
also tested the CLI to verify that it accepts either API.
> Proxysubmission from the Oozie client doesn't allow the mapreduce API
> ---------------------------------------------------------------------
>
> Key: OOZIE-1387
> URL: https://issues.apache.org/jira/browse/OOZIE-1387
> Project: Oozie
> Issue Type: Bug
> Components: client
> Affects Versions: 3.3.2
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Fix For: trunk
>
> Attachments: OOZIE-1387.patch
>
>
> The OozieClient looks for {{mapred.mapper.class}} and
> {{mapred.reducer.class}} so they have to be specified. If a user wants to use
> a mapper/reducer that inherits from mapreduce.Mapper/Reducer (i.e. mapreduce
> API), Oozie will force them to use mapred.mapper/reducer.class to specify
> their mapper/reducer, which will make Hadoop throw an exception during the
> job.
> We should update the checking to allow either {{mapred.mapper/reducer.class}}
> or {{mapreduce.mapper/reducer.class}} as long as one or the other is
> specified.
> This isn't a problem for a regular MR action or the REST API because its
> purely an Oozie client check (OozieCLI#mrCommand).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
