You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Ergin Demirel (JIRA)" <ji...@apache.org> on 2015/06/17 23:09:00 UTC
[jira] [Commented] (OOZIE-2101) all DAG workflow
[ https://issues.apache.org/jira/browse/OOZIE-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14590610#comment-14590610 ]
Ergin Demirel commented on OOZIE-2101:
--------------------------------------
[~grzegorz.chilkiewicz] any update on this issue? I can't see any activity for long time.
> all DAG workflow
> ----------------
>
> Key: OOZIE-2101
> URL: https://issues.apache.org/jira/browse/OOZIE-2101
> Project: Oozie
> Issue Type: Wish
> Reporter: Grzegorz Chilkiewicz
> Priority: Minor
>
> i'd read documentation about Oozie,
> it looks interesting, but i've a doubt:
> first web-page says "Oozie Workflow jobs are Directed Acyclical Graphs (DAGs) of actions."
> so i assumed it can deal with any DAG, but documentation says it is limited to specific subset of DAGs,
> ie: (DAG in ASCII art, directed top-down: )
> ....1
> .../.\
> ..2...\
> ./.\...\
> 3...4...5
> .\...\./
> ..\...6
> ...\./
> ....7
> can't be expressed in Oozie workflow
> (according to documentation: every join-node must join all branches of corresponding fork-node, so my ASCII DAG isn't valid Oozie workflow...)
> am i wrong? / why it's so limited? / is it intentional?
> //
> //if join-node could just wait until all IN-edges are traversed,
> //not necessary from any particular 'corresponding fork-node'
> //it would work for all DAGs.....
> //
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)