[
https://issues.apache.org/jira/browse/KAFKA-8828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916255#comment-16916255
]
Marcos Passos commented on KAFKA-8828:
--------------------------------------
The issue I’m facing is pretty much the same as Adams’s. I have a stream
application that performs a stateful transformation using a global store. Since
2.3, the context returns a TimestampedKeyValueStore which breaks any existing
application that relies on a plain global key-value store.
> [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)
