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

Posted to dev@kafka.apache.org by "Matthias J. Sax (Jira)" <ji...@apache.org> on 2019/12/09 03:24:00 UTC

[jira] [Resolved] (KAFKA-8953) Consider renaming `UsePreviousTimeOnInvalidTimestamp` timestamp extractor

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

Matthias J. Sax resolved KAFKA-8953.
------------------------------------
    Fix Version/s: 2.5.0
       Resolution: Fixed

> Consider renaming `UsePreviousTimeOnInvalidTimestamp` timestamp extractor
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-8953
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8953
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Matthias J. Sax
>            Assignee: Rabi Kumar K C
>            Priority: Trivial
>              Labels: beginner, kip, newbie
>             Fix For: 2.5.0
>
>
> Kafka Streams ships couple of different timestamp extractors, one named `UsePreviousTimeOnInvalidTimestamp`.
> Given the latest improvements with regard to time tracking, it seems appropriate to rename this class to `UsePartitionTimeOnInvalidTimestamp`, as we know have fixed definition of partition time, and also pass in partition time into the `#extract(...)` method, instead of some non-well-defined "previous timestamp".
> KIP-530: [https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=130028807]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)