[CASSANDRA-6060] Remove internal use of Strings for ks/cf names

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Won't Fix
• Component/s: Legacy/Streaming and Messaging
• Labels: performance
• Assignee: Ariel Weisberg
• Reporter: Jonathan Ellis

Authors

Ariel Weisberg

• Created: 19/Sep/13 15:42
• Updated: 16/Apr/19 09:32
• Resolved: 10/Dec/14 21:28

Description

We toss a lot of Strings around internally, including across the network. Once a request has been Prepared, we ought to be able to encode these as int ids.

Unfortuntely, we moved from int to uuid in CASSANDRA-3794, which was a reasonable move at the time, but a uuid is a lot bigger than an int. Now that we have CAS we can allow concurrent schema updates while still using sequential int IDs.

Issue Links

• is related to: CASSANDRA-5202 CFs should have globally and temporally unique CF IDs to prevent "reusing" data from earlier incarnation of same CF name