[ https://issues.apache.org/jira/browse/CASSANDRA-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nate McCall updated CASSANDRA-15245: ------------------------------------ Resolution: Not A Bug Status: Resolved (was: Triage Needed) Hi [~sarkara1], Cassandra 3.11 uses guava 18 which still contains CharMatcher.DIGIT. https://github.com/apache/cassandra/blob/cassandra-3.11/build.xml#L368 We use this specific matcher in a couple of critical places dealing with SSTable component filenames, so we would not compile if there were a mismatch. Please double check the dependency map via mvn dependency:tree or gradle dependencies to make sure you are not pulling in a different version of guava into your project. Further, I recommend taking a look simulacron instead of using cassandra-all for any sort of testing (assuming that is what you are doing): https://github.com/datastax/simulacron/tree/master/doc/java_api > cassandra-all| library uses non-existent Guava classes > ------------------------------------------------------ > > Key: CASSANDRA-15245 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15245 > Project: Cassandra > Issue Type: Bug > Components: Build, Dependencies, Packaging > Reporter: Abhijit Sarkar > Priority: Normal > > The > [cassandra-all|https://search.maven.org/artifact/org.apache.cassandra/cassandra-all/3.11.4/jar] > library references classes that have been removed from Guava, for example > {{com.google.common.base.CharMatcher.DIGIT}}. This causes runtime errors like > {code} > java.lang.NoClassDefFoundError: Could not initialize class > org.apache.cassandra.io.sstable.format.SSTableFormat$Type > {code} -- This message was sent by Atlassian JIRA (v7.6.14#76016) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org