Sachin Goyal created CASSANDRA-13383:
----------------------------------------
Summary: Confusing error: unconfigured table table2
Key: CASSANDRA-13383
URL: https://issues.apache.org/jira/browse/CASSANDRA-13383
Project: Cassandra
Issue Type: Improvement
Reporter: Sachin Goyal
*Select * from an_absent_table;* - gives an error:
com.datastax.driver.core.exceptions.InvalidQueryException: unconfigured table
an_absent_table
at
com.datastax.driver.core.Responses$Error.asException(Responses.java:136)
at
com.datastax.driver.core.DefaultResultSetFuture.onSet(DefaultResultSetFuture.java:179)
at
com.datastax.driver.core.RequestHandler.setFinalResult(RequestHandler.java:177)
at
com.datastax.driver.core.RequestHandler.access$2500(RequestHandler.java:46)
at
com.datastax.driver.core.RequestHandler$SpeculativeExecution.setFinalResult(RequestHandler.java:799)
at
com.datastax.driver.core.RequestHandler$SpeculativeExecution.onSet(RequestHandler.java:633)
at
com.datastax.driver.core.Connection$Dispatcher.channelRead0(Connection.java:1070)
at
com.datastax.driver.core.Connection$Dispatcher.channelRead0(Connection.java:993)
at
io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
This error should be more descriptive.
At the very least it should mention the keyspace where Cassandra was trying to
find the table.
It would help debug client code a lot faster if the keyspace was mentioned in
the above message.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
