[
https://issues.apache.org/jira/browse/APEXMALHAR-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388257#comment-15388257
]
ASF GitHub Bot commented on APEXMALHAR-2076:
--------------------------------------------
GitHub user brightchen reopened a pull request:
https://github.com/apache/apex-malhar/pull/294
APEXMALHAR-2076 #resolve #comment add AbstractTupleUniqueExactlyOnceK…
…afkaOutputOperator
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/brightchen/apex-malhar APEXMALHAR-2076
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/apex-malhar/pull/294.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #294
----
commit b45b6fdf66acdefe65a7fd0513e256460a5eb10f
Author: brightchen <[email protected]>
Date: 2016-05-25T20:01:26Z
APEXMALHAR-2076 #resolve #comment add
AbstractTupleUniqueExactlyOnceKafkaOutputOperator
----
> AbstractExactlyOnceKafkaOutputOperator didn't handle the orderless of tuples
> in a window
> ----------------------------------------------------------------------------------------
>
> Key: APEXMALHAR-2076
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2076
> Project: Apache Apex Malhar
> Issue Type: Bug
> Reporter: bright chen
> Assignee: bright chen
>
> The order of the tuples in the same window are not guaranteed in replay.
> AbstractExactlyOnceKafkaOutputOperator's logic assume the replayed tuples
> have same order.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
