mirror of
https://github.com/scylladb/scylladb.git
synced 2026-05-29 11:10:40 +00:00
Currently an exception is thrown in the apply stage when the schema is not synced, but it is too late since returning an error doesn't pinpoint which code path was using an unsync'ed schema so move the check earlier, before _apply_stage is called. We need to make sure the schema is synced earlier when the mutation is applied so call on_internal_error to generate a backtrace in testing and still throw an error in production. Typically storage_proxy::mutate_locally implicitly ensures the schema is synced by making a global_schema_ptr for it. Signed-off-by: Benny Halevy <bhalevy@scylladb.com> Message-Id: <20220424110057.3957597-1-bhalevy@scylladb.com>