Re: inexistent columns familes

got it thanks! will have to tackle this in another way. Thank you. Regards L. On Tue, Apr 17, 2018 at 1:58 PM, Jeff Jirsa wrote: > I imagine 3.0.16 has THIS bug, but it has far fewer other real bugs. > > > > On Tue, Apr 17, 2018 at 1:56 PM, Luigi Tagliamonte < >

Re: inexistent columns familes

I imagine 3.0.16 has THIS bug, but it has far fewer other real bugs. On Tue, Apr 17, 2018 at 1:56 PM, Luigi Tagliamonte < luigi.tagliamont...@gmail.com> wrote: > Thank you Jeff, > my backup scripts works using the cf folders on disk :) > it parses all the keyspaces and for each performs:

Re: inexistent columns familes

Thank you Jeff, my backup scripts works using the cf folders on disk :) it parses all the keyspaces and for each performs: nodetool flush ${keyspace} ${cf} and then nodetool snapshot ${keyspace} -cf ${cf} Does 3.0.16 not having this "bug"? Regards L. On Tue, Apr 17, 2018 at 1:50 PM, Jeff Jirsa

Re: inexistent columns familes

It's probably not ideal, but also not really a bug. We need to create the table in the schema to see if it exists on disk so we know whether or not to migrate it, and when we learn it's empty, we remove it from the schema but we dont delete the directory. It's not great, but it's not going to

inexistent columns familes

Hello everybody, i'm having a problem with a brand new cassandra:3.0.11 node. The following tables belonging to the system keyspace: - schema_aggregates - schema_columnfamilies - schema_columns - schema_functions - schema_keyspaces - schema_triggers - schema_usertypes get initialised on disk: