cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13426) Make all DDL statements idempotent and not dependent on global state
Date Thu, 12 Apr 2018 19:10:00 GMT


Aleksey Yeschenko commented on CASSANDRA-13426:

Status update: all unit tests are [passing|]
and so are all [dtests|]. {{}}
is the only failure on the branch, and it's unrelated - CASSANDRA-14371 is the JIRA for it.

Occasionally, {{}}
would fail too, because materialized views are amazing, and a subtle change in ordering of
local/remote schema application exposes an existing race condition in MV building. I'm not
going to fix it, as this patch is not the cause of the issue, but merely exposes it, and I
have better things to do with my life.

Next step: address review feedback and slightly optimise the diffing code to take into account
on-disk representation.

> Make all DDL statements idempotent and not dependent on global state
> --------------------------------------------------------------------
>                 Key: CASSANDRA-13426
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Distributed Metadata
>            Reporter: Aleksey Yeschenko
>            Assignee: Aleksey Yeschenko
>            Priority: Major
>             Fix For: 4.0
> A follow-up to CASSANDRA-9425 and a pre-requisite for CASSANDRA-10699.
> It's necessary for the latter to be able to apply any DDL statement several times without
side-effects. As part of the ticket I think we should also clean up validation logic and our
error texts. One example is varying treatment of missing keyspace for DROP TABLE/INDEX/etc.
statements with IF EXISTS.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message