Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-6060

Remove internal use of Strings for ks/cf names

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    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.

      Attachments

        Issue Links

        is related to

        Bug - A problem which impairs or prevents the functions of the product. CASSANDRA-5202 CFs should have globally and temporally unique CF IDs to prevent "reusing" data from earlier incarnation of same CF name

        • Normal -
        • Resolved

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            aweisberg Ariel Weisberg Assign to me
            jbellis Jonathan Ellis
            Ariel Weisberg
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment