You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You have a good point about the missing keyspace. It currently only throws an exception so that the pool can still be created and used even when the keyspace doesn't exist (e.g. you may to perform management operations to create the missing keyspace). However, that's probably not the usual use case...
Would it make sense to throw a exception when you try to connect to a cluster where the wanted is not added, or the column family is missing?
Currently, there is only log output. I think, a missing keyspace or columnFamily is rather severe and should cause an exception.
The text was updated successfully, but these errors were encountered: