cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thibault Kruse (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-14004) Increase Guava upstream version API compatibility
Date Thu, 09 Nov 2017 01:42:01 GMT
Thibault Kruse created CASSANDRA-14004:
------------------------------------------

             Summary: 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message