Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C829C200B52 for ; Mon, 25 Jul 2016 17:57:24 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C6929160A7D; Mon, 25 Jul 2016 15:57:24 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1C6B1160A67 for ; Mon, 25 Jul 2016 17:57:23 +0200 (CEST) Received: (qmail 58869 invoked by uid 500); 25 Jul 2016 15:57:23 -0000 Mailing-List: contact dev-help@apex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@apex.apache.org Delivered-To: mailing list dev@apex.apache.org Received: (qmail 58858 invoked by uid 99); 25 Jul 2016 15:57:23 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jul 2016 15:57:23 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id E2290C0373 for ; Mon, 25 Jul 2016 15:57:22 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -5.446 X-Spam-Level: X-Spam-Status: No, score=-5.446 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id ZGqOseoirzMb for ; Mon, 25 Jul 2016 15:57:22 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 67FC25F341 for ; Mon, 25 Jul 2016 15:57:21 +0000 (UTC) Received: (qmail 58317 invoked by uid 99); 25 Jul 2016 15:57:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jul 2016 15:57:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 7DC4D2C0D5D for ; Mon, 25 Jul 2016 15:57:20 +0000 (UTC) Date: Mon, 25 Jul 2016 15:57:20 +0000 (UTC) From: "Sandesh (JIRA)" To: dev@apex.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (APEXCORE-497) Create a DelayNode for DelayOperator MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 25 Jul 2016 15:57:25 -0000 [ 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)