cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13813) Don't let user drop (or generally break) tables in system_distributed
Date Tue, 10 Oct 2017 10:25:00 GMT


Aleksey Yeschenko commented on CASSANDRA-13813:

bq. My only bother is that while I haven't actually tried it recently, last time I did try
updating the schema tables manually, it was annoying because the changes were not automatically
picked-up and in fact tended to be overridden, so I had to force a reload in weird ways (altering
some other unrelated table in the keyspace, which here would actually be an issue). So it
would be nice if we added a JMX call to force reload schema tables from disk to make this
easier (should be easy). If we do, I'm warming up to the idea of considering this is the only
really safe work-around until we find a better way to deal with all thise.

Yep. You either do an unrelated {{ALTER}} (usually {{WITH comment = ...}}) or bounce the node.
Also wouldn't mind at all adding the new JMX call, as a companion to {{resetlocalschema}}.

> Don't let user drop (or generally break) tables in system_distributed
> ---------------------------------------------------------------------
>                 Key: CASSANDRA-13813
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Distributed Metadata
>            Reporter: Sylvain Lebresne
>            Assignee: Aleksey Yeschenko
>             Fix For: 3.0.x, 3.11.x
> There is not currently no particular restrictions on schema modifications to tables of
the {{system_distributed}} keyspace. This does mean you can drop those tables, or even alter
them in wrong ways like dropping or renaming columns. All of which is guaranteed to break
stuffs (that is, repair if you mess up with on of it's table, or MVs if you mess up with {{view_build_status}}).
> I'm pretty sure this was never intended and is an oversight of the condition on {{ALTERABLE_SYSTEM_KEYSPACES}}
in [ClientState|].
That condition is such that any keyspace not listed in {{ALTERABLE_SYSTEM_KEYSPACES}} (which
happens to be the case for {{system_distributed}}) has no specific restrictions whatsoever,
while given the naming it's fair to assume the intention that exactly the opposite.

This message was sent by Atlassian JIRA

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

View raw message