traces and auth in that version have a whitelist of tables that can be dropped (legacy auth tables).
https://github.com/apache/cassandra/blob/cassandra-3.0.12/src/java/org/apache/cassandra/service/ClientState.java#L367 <https://github.com/apache/cassandra/blob/cassandra-3.0.12/src/java/org/apache/cassandra/service/ClientState.java#L367> It does make sense to allowing CREATEs in the distributed tables, mostly because of auth. That way if the auth tables are changed in later version you can pre-prime them before an upgrade. Might be a bit of overstep in protecting users from themselves but it doesnt hurt anything to have the table there. Just ignore it and its existence will not cause any issues. Chris > On Mar 19, 2018, at 10:27 AM, shalom sagges <shalomsag...@gmail.com> wrote: > > That's weird... I'm using 3.0.12, so I should've still been able to drop it, > no? > > Also, if I intend to upgrade to version 3.11.2, will the existence of the > table cause any issues? > > Thanks! > > On Mon, Mar 19, 2018 at 4:30 PM, Chris Lohfink <clohf...@apple.com > <mailto:clohf...@apple.com>> wrote: > Oh I misread original, I see. > > With https://issues.apache.org/jira/browse/CASSANDRA-13813 > <https://issues.apache.org/jira/browse/CASSANDRA-13813> you wont be able to > drop the table, but would be worth a ticket to prevent creation in those > keyspaces or allow some sort of override if allowing create. > > Chris > > >> On Mar 19, 2018, at 9:15 AM, shalom sagges <shalomsag...@gmail.com >> <mailto:shalomsag...@gmail.com>> wrote: >> >> Yes, that's correct. >> >> I'd definitely like to keep the default tables. >> >> On Mon, Mar 19, 2018 at 4:10 PM, Rahul Singh <rahul.xavier.si...@gmail.com >> <mailto:rahul.xavier.si...@gmail.com>> wrote: >> I think he just wants to delete the test table not the whole keyspace. Is >> that correct? >> >> -- >> Rahul Singh >> rahul.si...@anant.us <mailto:rahul.si...@anant.us> >> >> Anant Corporation >> >> On Mar 19, 2018, 9:08 AM -0500, Chris Lohfink <clohf...@apple.com >> <mailto:clohf...@apple.com>>, wrote: >>> No. >>> >>> Why do you want to? If you don't use tracing they will be empty, and if >>> were able to drop them you will no longer be able to use tracing in >>> debugging. >>> >>> Chris >>> >>>> On Mar 19, 2018, at 7:52 AM, shalom sagges <shalomsag...@gmail.com >>>> <mailto:shalomsag...@gmail.com>> wrote: >>>> >>>> Hi All, >>>> >>>> I accidentally created a test table on the system_traces keyspace. >>>> >>>> When I tried to drop the table with the Cassandra user, I got the >>>> following error: >>>> Unauthorized: Error from server: code=2100 [Unauthorized] message="Cannot >>>> DROP <table system_traces.test12321>" >>>> >>>> Is there a way to drop this table permanently? >>>> >>>> Thanks! >>> >> > >
