Consider exposing awaitSchemaAgreement

[muirdm]

Wanted to see what others thought about adding func (*Session).AwaitSchemaAgreement() error as a public method.

I'm running schema changes from gocql and I want to make sure the schema is in agreement after every schema change. gocql has built-in calls to awaitSchemaAgreement, but it doesn't propagate an error. I could query system.peers myself, but you also need to query the coordinator's system.local to get the full list. gocql doesn't really provide a way to query a specific node (that I know of) short of making a second cluster with host limiting config. It would be convenient if I could just depend on gocql's already implemented logic to check the entire ring's schema version.

[alourie]

@Zariel your opinion? I can make the change as a part of #1300

[annismckenzie]

I added this in #1395 – I'd like to use it in gocqlx's issue scylladb/gocqlx#106 to await schema agreement before applying each statement in a migration. Thoughts?

[annismckenzie]

This was added in #1395. Close this issue?

[alourie]

@annismckenzie Please do :-) Thanks!

[annismckenzie]

I can't! :D

[alourie]

haha, fine :-)