> > Something like "TABLESPACE" or 'TABLEGROUP" would *theoretically* better > satisfy point 1 and 2 above but subjectively I kind of recoil at both > equally. So there's that. >
TABLEGROUP would work for me. Immediately intuitive. brain-storming… A keyspace today defines replication strategy, rf, and durable_writes. If they also had the table options that could be defined as defaults for all tables in that group, and one tablegroup could be a child and inherit settings from another tablegroup, you could logically group tables in ways that both benefit your application platform's taxonomy and the spread of keyspace/table settings. DATABASE, NAMESPACE, whatever, can be aliases to it too, if you like.
