[ https://issues.apache.org/jira/browse/KAFKA-8828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16917321#comment-16917321 ]
Marcos Passos edited comment on KAFKA-8828 at 8/28/19 2:01 AM: --------------------------------------------------------------- Matthias, I think you get me wrong. I'm not injecting a global store through the constructor. The stream application’s topology includes a global store created using `StreamBuilder.addGlobalStore`. Then, in the `Transformer::init()`, I retrieve it as a read-only store. How does it can be considered bad practice? Nonetheless, I’m using the public API in a non-hacky way, so I expect it to do not break in a minor release. * [|https://issues.apache.org/jira/secure/AddComment!default.jspa?id=13252679] was (Author: marcospassos): Matthias, I think you get me wrong. I'm not injecting a global store through de constructor. The stream application’s topology includes a global store created using `StreamBuilder.addGlobalStore`. Then, in the `Transformer::init()`, I retrieve it as a read-only store. How does it can be considered bad practice? Nonetheless, I’m using the public API in a non-hacky way, so I expect it to do not break in a minor release. > [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)