I’m reasonably certain that this is one of the things that I fixed in 4.0. It’d be too invasive a change for 3.11, unfortunately.
> On 1 Sep 2020, at 16:52, Benjamin Lerer <benjamin.le...@datastax.com> wrote: > > Hi, > > Could you precise what you mean by " will only validate the schema while > changing in memory, and will not validate before flush to disk.". It is > unclear to me of which validation you are talking about. > > > > > > On Tue, Sep 1, 2020 at 1:44 PM Weiliang Zhang <394693...@qq.com> wrote: > >> Does anyone has any ideas? >> >> On 2020/08/31 10:07:30, weiliang zhang<394693...@qq.com> wrote: >>> Hi everyone, I found that cassandra will first flush new schema to disk >> and then change in memory while updating schema in Cassandra3.11.4 >> (SchemaKeyspace.java:1378) . >>> But it seems that cassandra will only validate the schema while changing >> in memory, and will not validate before flush to disk. >>> I don't know why not validate before flushing to disk ? Some request >> will succeed in updating schema to disk and fail to update schema in >> memory, which will make the schema in disk and schema in memory are not >> consistent. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org >>> For additional commands, e-mail: dev-h...@cassandra.apache.org >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org >> For additional commands, e-mail: dev-h...@cassandra.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
