apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pramod Immaneni (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-339) Support ability to tag operators as idempotent or non-idempotent
Date Wed, 02 Mar 2016 15:39:18 GMT

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

Pramod Immaneni commented on APEXCORE-339:
------------------------------------------

For input operators same data in same window on replay, for operators that are non input give
same input produce same output.

> Support ability to tag operators as idempotent or non-idempotent
> ----------------------------------------------------------------
>
>                 Key: APEXCORE-339
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-339
>             Project: Apache Apex Core
>          Issue Type: Bug
>            Reporter: Pramod Immaneni
>            Assignee: Pramod Immaneni
>
> Certain application require idempotency and some others don't. Additionally operators
such as input operators need to be specially instrumented to exhibit idempotent behavior.
Certain output operators like database operators rely on idempotency. For these reasons we
need ability to label operators as idempotent or now, whether output operators require idempotency
from upstream operators or not. In case of a failure the platform should handle non-idempotent
streams by restarting the failed operator and all downsteram operators at the same checkpoint.



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

Mime
View raw message