[FOLLOW UP QUESTION TO #11943]
I have a follow up question. Currently, we throttle the amount of concurrent Cassandra activity by limiting the number of background threads that are dropping-creating tables. However, within these threads our application issues the DDL commands through the Java driver in sequence. To be safe, it sounds like we should be waiting for a pause in this activity before issuing the next command. Does the Java driver have support for either waiting (synchronous) or event listeners (asynchronous) that could signal our application when a previously issued schema change has been completely processed? Given the latency of processing schema changes across a Cassandra cluster, it seems that a feature like this would be important in order to avoid schema corruption.