...
Current state: Under Discussion
Discussion thread: https://lists.apache.org/x/thread.html/rb942356f03c4a1e3d313eb20548129f6c508777a327935af169c60d2@%3Cdev.kafka.apache.org%3E
JIRA:
Jira | ||||||
---|---|---|---|---|---|---|
|
...
We remove the config value without first deprecating it in Java code because we effectively deprecated it 2.5 by choosing latest
as the default value for built.in.metrics.version
and by not really documenting config value stating in KIP-444 that 0.10.0-2.4
in the monitoring documentation was introduced to allow users having a grace period of changing their corresponding monitoring. For future additions of new values to this config, we plan to deprecate the should improve by officially deprecating values other than latest
right away when the values are introduced.
...
Config value 0.10.0-2.4
of config built.in.metrics.version
will be removed in AK 3.0.0 with no replacement. Users that set 0.10.0-2.4
need to switch to config value latest
and adapt their monitoring.
Rejected Alternatives
- Removing the complete config
built.in.metrics.version:
The config can still be used for future changes to the built-in metrics. - Deprecating config value
0.10.0-2.4
:
The config value was effectively deprecated when it was introduced, so that we think we can remove the config value right away without causing too much troubles.