Cassandra Connector: java.lang.NoClassDefFoundError: io/netty/util/Timer

The presto-cli fails with Query is gone (server restarted?) when trying to describe a table from Cassandra.

Error at presto server side:

WARN    statement-response-5    com.facebook.presto.server.ThrowableMapper      Request failed for /v1/statement/20200321_162656_00004_8zbfq/1
java.lang.NoClassDefFoundError: io/netty/util/Timer
        at com.datastax.driver.core.Configuration$Builder.build(Configuration.java:317)
        at com.datastax.driver.core.Cluster$Builder.getConfiguration(Cluster.java:1282)
        at com.datastax.driver.core.Cluster.<init>(Cluster.java:113)
        at com.datastax.driver.core.Cluster.buildFrom(Cluster.java:178)
        at com.datastax.driver.core.Cluster$Builder.build(Cluster.java:1299)
        at com.facebook.presto.cassandra.CassandraClientModule.lambda$createCassandraSession$0(CassandraClientModule.java:149)
        at com.facebook.presto.cassandra.ReopeningCluster.delegate(ReopeningCluster.java:54)
        at com.datastax.driver.core.DelegatingCluster.getConfiguration(DelegatingCluster.java:96)
        at com.facebook.presto.cassandra.NativeCassandraSession.executeWithSession(NativeCassandraSession.java:531)
        at com.facebook.presto.cassandra.NativeCassandraSession.getKeyspaceByCaseInsensitiveName(NativeCassandraSession.java:257)
        at com.facebook.presto.cassandra.NativeCassandraSession.getTable(NativeCassandraSession.java:190)
        at com.facebook.presto.cassandra.CassandraMetadata.getTableHandle(CassandraMetadata.java:104)
        at com.facebook.presto.cassandra.CassandraMetadata.getTableHandle(CassandraMetadata.java:66)
        at com.facebook.presto.metadata.MetadataManager.getTableHandle(MetadataManager.java:331)
        at com.facebook.presto.sql.rewrite.ShowQueriesRewrite$Visitor.visitShowColumns(ShowQueriesRewrite.java:371)
        at com.facebook.presto.sql.rewrite.ShowQueriesRewrite$Visitor.visitShowColumns(ShowQueriesRewrite.java:154)
        at com.facebook.presto.sql.tree.ShowColumns.accept(ShowColumns.java:54)
        at com.facebook.presto.sql.tree.AstVisitor.process(AstVisitor.java:27)
        at com.facebook.presto.sql.rewrite.ShowQueriesRewrite.rewrite(ShowQueriesRewrite.java:151)
        at com.facebook.presto.sql.rewrite.StatementRewrite.rewrite(StatementRewrite.java:53)
        at com.facebook.presto.sql.analyzer.Analyzer.analyze(Analyzer.java:76)
        at com.facebook.presto.sql.analyzer.Analyzer.analyze(Analyzer.java:71)
        at com.facebook.presto.execution.SqlQueryExecution.<init>(SqlQueryExecution.java:194)
        at com.facebook.presto.execution.SqlQueryExecution.<init>(SqlQueryExecution.java:96)
        at com.facebook.presto.execution.SqlQueryExecution$SqlQueryExecutionFactory.createQueryExecution(SqlQueryExecution.java:733)
        at com.facebook.presto.execution.SqlQueryManager.createQueryInternal(SqlQueryManager.java:366)
        at com.facebook.presto.execution.SqlQueryManager.lambda$createQuery$4(SqlQueryManager.java:304)
        at com.facebook.presto.$gen.Presto_0_233_e343965____20200321_162135_1.run(Unknown Source)
        at com.facebook.airlift.concurrent.BoundedExecutor.drainQueue(BoundedExecutor.java:78)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.ClassNotFoundException: io.netty.util.Timer
        at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
        at com.facebook.presto.server.PluginClassLoader.loadClass(PluginClassLoader.java:80)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
        ... 32 more

How to solve this dependency issue?

[rschlussel]

fix should be in the 0.237 release

[Ennosigaeon]

@codekaust We recently switched to PrestoSQL due to JSON support. So I am not sure, if any newer version would work. The changes that broke Cassandra were introduced between releases 0.228 and 0.229. We initially observed the problems in version 0.332.