I want to know
Does JDBC needs predefined cassandra column family structure?
Means should i create column family schema prior to inserting data into column family
In an effort to consolidate free help offered for our products we have decided to move these forums to a more widely used forum. Please use one of the following queries (or any combination):
- Cassandra: tag search or plain text search
- DataStax Enterprise: tag search or plain text search
- DataStax OpsCenter: tag search or plain text search
JDBC interaction with Cassandra(6 posts) (3 voices)
Yes, you need to create your schema before using JDBC.
Thanks for the reply, one more thing which i like to know is ,can i insert different columns which i have not specified in schema definition?
Because i tried , and it failed.
I don't know about JDBC but if you want to insert columns that you don't have in your schema you can use Thrift which allows that for sure.
I want to understand that how cassandra ensures high availability. What i know is when we query casssandra database for data, a node called coordinator route the query to the appropriate cassandra node in the cluster with the required data. But what if the node which we specify in JDBC connection URL (Which i think will act as coordinator in the cluster, please make me correct if i am wrong) itself down? In this case how come cassandra ensures high availability?
Perhaps we as a developer must provide fallback mechanism for that?
Please help me out to understand this.
That's right, the client software must be able to reconnect to a different node if the coordinator goes down. Ideally the CQL driver or other Cassandra connector library would take care of that for you, but not all of them do yet.