Jeff, The issue I was trying to address is when there are two CREATE TABLE queries running on two coordinator nodes concurrently, it might end up with 2 schema versions and they would never get resolved automatically because table id is random TimeUUID.
On Mon, Aug 8, 2022 at 3:54 PM Jeff Jirsa <jji...@gmail.com> wrote: > Which (of the many) schema disagreement issue(s)? > > > > On Mon, Aug 8, 2022 at 3:29 PM Cheng Wang via dev < > dev@cassandra.apache.org> wrote: > >> Thank you for the reply, Brandon! It is helpful! >> >> I was thinking of creating a cluster with 2 nodes and having two >> concurrent CREATE TABLE statements running. But the test will be flaky as >> there is no guarantee that the query runs before the schema agreement has >> been reached. >> Any ideas for that? >> >> Thanks, >> Cheng >> >> On Mon, Aug 8, 2022 at 3:19 PM Brandon Williams <dri...@gmail.com> wrote: >> >>> If you simply do a lot of schema changes quickly without waiting for >>> agreement, that should get you there. >>> >>> Kind Regards, >>> Brandon >>> >>> On Mon, Aug 8, 2022 at 5:08 PM Cheng Wang via dev >>> <dev@cassandra.apache.org> wrote: >>> > >>> > Hello, >>> > >>> > I am working on improving the schema disagreement issue. I need some >>> dtests which can reproduce the schema disagreement. Anyone know if there >>> are any existing tests for that? Or something similar? >>> > >>> > Thanks >>> > Cheng >>> >>
