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 2019/08/25 18:53:00 UTC
[jira] [Commented] (KAFKA-8828) [BC Break] Global store returns a
TimestampedKeyValueStore in 2.3
[ https://issues.apache.org/jira/browse/KAFKA-8828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915317#comment-16915317 ]
Matthias J. Sax commented on KAFKA-8828:
----------------------------------------
Can you elaborate? Since 2.3, `GlobalKTable` use timestamped stores. However, manually added global stores should not be affected. However, if you add a `GlobalKTable` you don't need to write any code and you would never need to access the `ProcessorContext`. What are you exactly trying to do? The change of [https://cwiki.apache.org/confluence/display/KAFKA/KIP-258%3A+Allow+to+Store+Record+Timestamps+in+RocksDB] should be backward compatible.
> [BC Break] Global store returns a TimestampedKeyValueStore in 2.3
> -----------------------------------------------------------------
>
> Key: KAFKA-8828
> URL: https://issues.apache.org/jira/browse/KAFKA-8828
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 2.3.0
> Reporter: Marcos Passos
> Priority: Major
>
> Since 2.3, {{ProcessorContext}} returns a {{TimestampedKeyValueStore}} for global stores, which is backward incompatible. This change makes the upgrade path a lot painful and involves creating a non-trivial adapter to hide the timestamp-related functionality in cases where it is not needed.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)