You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Matthias J. Sax (JIRA)" <ji...@apache.org> on 2018/02/20 03:04:00 UTC

[jira] [Updated] (KAFKA-6455) Improve timestamp propagation at DSL level

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

Matthias J. Sax updated KAFKA-6455:
-----------------------------------
    Description: At DSL level, we inherit the timestamp propagation "contract" from the Processor API. This contract in not optimal at DSL level, and we should define a DSL level contract that matches the semantics of the corresponding DSL operator.  (was: At DSL level, we inherit the timestamp propagation "contract" from the Processor API. This contract in not optimal at DSL level, and we should define a DSL level contract that matches the semantics of the corresponding DSL operator.

This ticket is only about *defining* the contract.)

> Improve timestamp propagation at DSL level
> ------------------------------------------
>
>                 Key: KAFKA-6455
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6455
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>    Affects Versions: 1.0.0
>            Reporter: Matthias J. Sax
>            Priority: Major
>              Labels: needs-kip
>
> At DSL level, we inherit the timestamp propagation "contract" from the Processor API. This contract in not optimal at DSL level, and we should define a DSL level contract that matches the semantics of the corresponding DSL operator.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)