falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abou Haydar Elias (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-349) Support "MapReduce" workflow in process entity
Date Tue, 23 Sep 2014 11:58:34 GMT

    [ https://issues.apache.org/jira/browse/FALCON-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144712#comment-14144712

Abou Haydar Elias commented on FALCON-349:

We can also consider it as if the oozie workflow configuration as a part of the process entity
XML with a higher level of abstraction. So +1  on what [~jb@nanthrax.net] suggest.

> Support "MapReduce" workflow in process entity
> ----------------------------------------------
>                 Key: FALCON-349
>                 URL: https://issues.apache.org/jira/browse/FALCON-349
>             Project: Falcon
>          Issue Type: Wish
>          Components: process
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
> Currently, a process entity supports the following workflow:
> - oozie
> - pig
> - hive
> If an user has a "pure" MapReduce job, the only way to use it in Falcon is via the oozie
workflow. It means he has to create the workflow.xml describing the nodes (mapred.mapper.class,
etc elements).
> So, it may look like a overhead for the user who just wants to "schedule" the job/process.
> I would propose to create a "mapreduce" workflow, taken directly a MapReduce jar from
the filesystem, and behind the hood, create a simple workflow.xml and schedule it in oozie.
> Thoughts ?

This message was sent by Atlassian JIRA

View raw message