[v2.0.0] Please wait for schema agreement on table creation

[sroebuck]

In a clustered cassandra environment I'm hitting occassional errors in code which creates a table and then immediately starts writing into it. The errors appear in the cassandra log as org.apache.cassandra.db.UnknownColumnFamilyException: Got slice command for nonexistent table my.test. If the table was just created, this is likely due to the schema not being fully propagated. Please wait for schema agreement on table creation.

Googling this issue it appears that this issue may be handled by other drivers by waiting for schema agreement before returning from the CREATE TABLE call.

There's a related StackOverflow response here, to quote:

The modern DataStax drivers automatically check and wait for schema agreement after you execute a schema-altering statement. Cassandra returns a special response for schema-altering statements that allows the drivers to do this automatically. Once the drivers gets that response, it (blockingly) queries the system.peers table of the node the query was executed against to check the reported schema versions of other nodes. It will continue to execute this query in a loop until either schema agreement is reached or a timeout is hit.

[AlexPikalov]

Looks as if it makes sense to investigate this more closely.
Thank you.