[
https://issues.apache.org/jira/browse/APEXCORE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064800#comment-15064800
]
ASF GitHub Bot commented on APEXCORE-3:
---------------------------------------
GitHub user tweise opened a pull request:
https://github.com/apache/incubator-apex-core/pull/189
APEXCORE-3 Module Support REBASED
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tweise/incubator-apex-core devel-3
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-apex-core/pull/189.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #189
----
commit e32adb9fa7b1b76016b815d00be7df947ed4f46f
Author: Vlad Rozov <[email protected]>
Date: 2015-09-24T03:30:51Z
APEX-103 - Add module and dag interface in API
commit c804774b86ae4c09dbd7ae4abb84d9fd64c510b6
Author: bhupeshchawda <[email protected]>
Date: 2015-10-06T07:04:24Z
APEXCORE-194 Added support for proxy ports
Added test cases.
commit 35b3c4e9544d89e57359844ccb9188aff0496461
Author: Tushar R. Gosavi <[email protected]>
Date: 2015-10-06T08:18:53Z
APEXCORE-105 Introduce module meta
Inject properties through xml file on modules.
commit 3caeb0e38d3b66b58485dbb09b4666e6136ba11b
Author: chinmaykolhatkar <[email protected]>
Date: 2015-10-07T09:36:36Z
APEXCORE-104 Added flattening of module into parent DAG
commit dff6017847628e13743c071da1bbe0bbbf4089b2
Author: shubham <[email protected]>
Date: 2015-11-17T06:40:08Z
APEXCORE-144, APEXCORE-145 Rest api changes to view module information
----
> Ability for an operator to populate DAG at launch time
> ------------------------------------------------------
>
> Key: APEXCORE-3
> URL: https://issues.apache.org/jira/browse/APEXCORE-3
> Project: Apache Apex Core
> Issue Type: New Feature
> Reporter: Amol Kekre
> Assignee: Vlad Rozov
> Priority: Critical
>
> Apex should have an operator API that lets the operator generate DAG during
> launch time. This will mean the following
> - Logical DAG will have one operator. This is the operator that will generate
> a DAG underneath
> - Physical plan will have the DAG generated by the operator
> - Execution plan will mimic physical plan + container location etc.
> For example lets say we have three operators in a DAG (app) A->B->C
> B during launch time generates a DAG B1->B2->B3, then the physical plan will
> be
> A->B1->B2->B3->C
> This should work irrespective of number of ports, etc. A typical flattening.
> The operators inside of B (B1, B2, B3) should have properties and attributes
> just as any. Users should be able to access these at run time and compile
> time. B itself should support properties and attributes that B1, B2, B3 can
> inherit from.
> This is a very critical feature as it will open up users to plug-in their own
> engines and still take up complete operability support from Apex engine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
