[
https://issues.apache.org/jira/browse/APEXCORE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225223#comment-15225223
]
Pramod Immaneni edited comment on APEXCORE-339 at 6/7/16 10:54 PM:
-------------------------------------------------------------------
Follow development here
https://github.com/PramodSSImmaneni/incubator-apex-core/tree/APEXCORE-339
was (Author: pramodssimmaneni):
Follow development here
https://github.com/PramodSSImmaneni/incubator-apex-core/tree/idempotence-recovery
> 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)
