[
https://issues.apache.org/jira/browse/APEXCORE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174514#comment-15174514
]
Pramod Immaneni commented on APEXCORE-339:
------------------------------------------
An annotation will be used to mark operators as idempotent, non-idempotent or
default. If no idempotency is specified it will be treated as default where
input operators are non-idempotent unless specified and non-input operators are
idempotent. Operators can also specify using an annotation that they require
idempotency from upstream pipeline such as output operators. Will post the
development branch soon.
> 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)
