You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Xinyu Liu (JIRA)" <ji...@apache.org> on 2017/11/21 19:36:00 UTC

[jira] [Updated] (SAMZA-1351) Separate Watermark Implementation from Propagation

     [ https://issues.apache.org/jira/browse/SAMZA-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xinyu Liu updated SAMZA-1351:
-----------------------------
    Fix Version/s: 0.14.0

> Separate Watermark Implementation from Propagation
> --------------------------------------------------
>
>                 Key: SAMZA-1351
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1351
>             Project: Samza
>          Issue Type: Task
>    Affects Versions: 0.14.0
>            Reporter: Xinyu Liu
>            Assignee: Xinyu Liu
>             Fix For: 0.14.0
>
>
> Based on Chris's feedback, I need to separate watermark implementation with propagation mechanism. Here is the feedback:
> - I expected Watermark just to be a value object but that doesn't agree with the propagate method, which looks out of place. As a user I should be able to set an arbitrary watermark. This method suggests that I must first receive a watermark then copy it. If we have the former, this looks to be unnecessary.
> - We seem to be mixing two ideas here... the watermark itself with its mechanism for propagation. It would be cleaner to provide these at the fluent API level (this is how flink works) and to do the right default operation for typical operations. Ultimately the user needs to be able to override this behavior though and I'm not seeing that capability so far in the design.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)