You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Rabi Kumar K C (Jira)" <ji...@apache.org> on 2019/10/02 12:50:00 UTC
[jira] [Issue Comment Deleted] (KAFKA-8953) Consider renaming
`UsePreviousTimeOnInvalidTimestamp` timestamp extractor
[ https://issues.apache.org/jira/browse/KAFKA-8953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rabi Kumar K C updated KAFKA-8953:
----------------------------------
Comment: was deleted
(was: Hi [~mjsax] Wrote emails to [dev@kafka.apache.org|mailto:dev@kafka.apache.org] but didn't get any response regarding permission. Would you able to help in this scenario? Confluence id: rabikumar.kc)
> 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, needs-kip, newbie
>
> 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".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)