[
https://issues.apache.org/jira/browse/KAFKA-8897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16931665#comment-16931665
]
Matthias J. Sax commented on KAFKA-8897:
----------------------------------------
{quote}Seems like the lack of deprecation if anything means we can only do it
in a major release. But if we do want to do it in a minor release, I think we
should at least just log a warning in 2.4 if that method is called and delay
the upgrade until 2.5.
{quote}
I don't see how we can do this?
While I agree with the incentive to not break compatibility, I don't see a way
how *_we_* could deprecate anything? We don't control `CompactionOptionsFIFO`
and if user code creates this class, how could we possible intercept the call
to `setTtl()` and log a warning? We only control `Options` that we pass as
method parameter.
> Increase Version of RocksDB
> ---------------------------
>
> Key: KAFKA-8897
> URL: https://issues.apache.org/jira/browse/KAFKA-8897
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Bruno Cadonna
> Priority: Major
>
> A higher version (6+) of RocksDB is needed for some metrics specified in
> KIP-471.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
