[ https://issues.apache.org/jira/browse/KAFKA-13699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503214#comment-17503214 ]
Matthias J. Sax commented on KAFKA-13699: ----------------------------------------- Seems the only question is, if we need to update the KIP? And if we can only fix forward in 3.2.0 (or if we can back-port to `3.0.1` and `3.1.1` ? \cc [~mimaison] [~guozhang] WDYT? `3.0.1` is already on it's way... > ProcessorContext does not expose Stream Time > -------------------------------------------- > > Key: KAFKA-13699 > URL: https://issues.apache.org/jira/browse/KAFKA-13699 > Project: Kafka > Issue Type: Bug > Components: streams > Affects Versions: 2.7.0 > Reporter: Shay Lin > Priority: Major > Labels: newbie > > As a KS developer, I would like to leverage > [KIP-622|https://cwiki.apache.org/confluence/display/KAFKA/KIP-622%3A+Add+currentSystemTimeMs+and+currentStreamTimeMs+to+ProcessorContext] > and access stream time in Processor Context. > _(Updated)_ > However, the methods currentStreamTimeMs or currentSystemTimeMs is missing > from for KStreams 3.0+. > Checked with [~mjsax] , the methods are absent from the Processor API , i.e. > * org.apache.kafka.streams.processor.api.ProcessorContext -- This message was sent by Atlassian Jira (v8.20.1#820001)