[
https://issues.apache.org/jira/browse/CASSANDRA-14004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245155#comment-16245155
]
Thibault Kruse commented on CASSANDRA-14004:
--------------------------------------------
fair enough, close if you want. Might still be worth thinking about how to deal
with future guava incompatibilities for cassandra 4.x +
> Increase Guava upstream version API compatibility
> -------------------------------------------------
>
> Key: CASSANDRA-14004
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14004
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Thibault Kruse
> Priority: Minor
>
> Using cassandra-all as a java library has the downside that it uses guava 18
> methods that have been removed from more recent guava versions, causing users
> to be forced to stick with Guava <= 19.0.
> It would be nice for us if such method calls to guava could be replaced with
> code of higher compatibility, for Casandra versions as far back as 3.0.x
> As an example replacing code like this
> Iterators.<RangeTombstone>emptyIterator()
> with
> Collections.emptyIterator()
> as done in
> https://github.com/krummas/cassandra/commits/marcuse/guava23
> Ensuring any cassandra-release is API compatible with several guava versions
> is more painful, possibly a blacklist of method calls can be used via
> checkstyle to reduce the risk of re-introducing version specific calls to
> guava methods.
> Related to the Guava upgrade ticket:
> https://issues.apache.org/jira/browse/CASSANDRA-13997
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
