apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandesh (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (APEXCORE-497) Create a DelayNode for DelayOperator
Date Mon, 25 Jul 2016 15:57:20 GMT

    [ https://issues.apache.org/jira/browse/APEXCORE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392152#comment-15392152
] 

Sandesh edited comment on APEXCORE-497 at 7/25/16 3:56 PM:
-----------------------------------------------------------

After reviewing the code and seeing that it is possible to implement it cleanly, this jira
has been filed. Ot cleanly separates the delay operator code from the regular path, which
is majority of our use case. At least few people liked it, so I am documenting the idea.


was (Author: sandesh):
After reviewing the code and seeing that it is possible to implement it cleanly, this jira
has been filed. I believe it cleanly separates the delay operator code from the regular path,
which is majority of our use case. At least few people liked it, so I am documenting the idea.

> Create a DelayNode for DelayOperator
> ------------------------------------
>
>                 Key: APEXCORE-497
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-497
>             Project: Apache Apex Core
>          Issue Type: Improvement
>            Reporter: Sandesh
>
> One of the design elements I have seen in Apex is, while deploying only required objects
are deployed. For example Stream persistence reservoir was created only when it is required.
So in the same spirit, we can have the DelayNode for Delay Operators.
> Delay Operator related changes happen for the control tuples in GenericNode.
> Implementation Idea: 
> 1. Create functions for handling each control tuples in Generic Node
> 2. DelayNode extends GenericNode
> 3. Overrides the required functions created in step 1.
> 4. During deployment based on the operator type, create the required Node.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message