apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Weise (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (APEXMALHAR-2283) Refactor kafka output operator
Date Mon, 10 Oct 2016 22:29:20 GMT

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

Thomas Weise edited comment on APEXMALHAR-2283 at 10/10/16 10:28 PM:
---------------------------------------------------------------------

The hashCode() assumption isn't documented. It is also not sufficient, there should be control
in the operator itself how the hash code is computed. I think we should revisit the options
for tracking the state.
 
Is there an example someone can start from for this operator? Documentation?


was (Author: thw):
The hashCode() assumption isn't documented. It is also not sufficient, there should be control
in the operator itself how the hash code is computed. I think we should revisit the options
for tracking the state.
 

> Refactor kafka output operator
> ------------------------------
>
>                 Key: APEXMALHAR-2283
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2283
>             Project: Apache Apex Malhar
>          Issue Type: Improvement
>            Reporter: Siyuan Hua
>            Assignee: Siyuan Hua
>
> The abstract kafka output operator needs to be refactored
> 1. Needs to set some mandatory properties on operator level instead of kafka property
level.
> 2. More document and examples
> 3. Find a standard way to achieve exactly once in both 0.8 and 0.9
> More will be added when working on the ticket



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

Mime
View raw message