apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frew, Troy" <Troy.F...@capitalone.com>
Subject Re: [jira] [Updated] (APEXCORE-3) Ability for an operator to populate DAG at launch time
Date Mon, 04 Jan 2016 17:01:13 GMT
Unsubscribe

Troy Frew
703.728.4309
Lead Systems Integrator
Troy.Frew@capitalone.com




On 12/29/15, 6:44 PM, "Sasha Parfenov (JIRA)" <jira@apache.org> wrote:

>
>     [ 
>https://issues.apache.org/jira/browse/APEXCORE-3?page=com.atlassian.jira.p
>lugin.system.issuetabpanels:all-tabpanel ]
>
>Sasha Parfenov updated APEXCORE-3:
>----------------------------------
>    Labels: roadmap  (was: )
>
>> 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
>>              Labels: roadmap
>>             Fix For: 3.3.0
>>
>>
>> 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)

________________________________________________________

The information contained in this e-mail is confidential and/or proprietary to Capital One
and/or its affiliates and may only be used solely in performance of work or services for Capital
One. The information transmitted herewith is intended only for use by the individual or entity
to which it is addressed. If the reader of this message is not the intended recipient, you
are hereby notified that any review, retransmission, dissemination, distribution, copying
or other use of, or taking of any action in reliance upon this information is strictly prohibited.
If you have received this communication in error, please contact the sender and delete the
material from your computer.


Mime
View raw message