[
https://issues.apache.org/jira/browse/KAFKA-12519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17306460#comment-17306460
]
Guozhang Wang commented on KAFKA-12519:
---------------------------------------
Hmm, do you mean that, when user upgrade to 3.0, even with the config removed,
we should still remember what's the old value of that config and then if it is
not "latest" we still execute the old path? Otherwise, why don't we just do
both steps in 3.0?
> Consider Removing Streams Old Built-in Metrics Version
> -------------------------------------------------------
>
> Key: KAFKA-12519
> URL: https://issues.apache.org/jira/browse/KAFKA-12519
> Project: Kafka
> Issue Type: Task
> Components: streams
> Reporter: Bruno Cadonna
> Priority: Major
> Fix For: 3.0.0
>
>
> We refactored the Streams' built-in metrics in KIP-444 and the new structure
> was released in 2.5. We should consider removing the old structure in the
> upcoming 3.0 release. This would give us the opportunity to simplify the code
> around the built in metrics since we would not need to consider different
> versions anymore.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
