[
https://issues.apache.org/jira/browse/CASSANDRA-15248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413418#comment-17413418
]
Tatu Saloranta commented on CASSANDRA-15248:
--------------------------------------------
Aside from actual upgrade, would it be possible to increase compatibility first
by – for example – replacing use of `CharMatcher.DIGIT` (which is one problem)
with something that is available on later versions?
Many OSS libraries work hard to try to work with wide(r) range of Guava
versions, being that Guava compatibility is a rather hard problem due to its
ubiquity – and I 100% agree that it is often not easy or safe to "just upgrade
to the latest Guava", at least if the current dep is to version below 23.0.
This comment is in particular wrt pre-4.0 Cassandra.
(for those interested, I wrote a bit about Guava compatibility wrt Jackson
Guava datatype module here:
[https://cowtowncoder.medium.com/jackson-guava-compatibility-b0b61ac59b28] )
where I have tried to avoid this module being the bottleneck wrt compatibility.
> Upgrade Guava to latest on master branch
> ----------------------------------------
>
> Key: CASSANDRA-15248
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15248
> Project: Cassandra
> Issue Type: Task
> Components: Build, Dependencies, Packaging
> Reporter: Abhijit Sarkar
> Priority: Normal
>
> Upgrade Guava to latest on master branch. See
> https://issues.apache.org/jira/browse/CASSANDRA-15245.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
