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

Fix issue with system.local.broadcast_port when downgrading to v3

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

Details

    • Bug
    • Status: Triage Needed
    • Normal
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      system.local table 4.0 format adds the broadcast_port column.  There is no way to make 3.x ignore it when we try to downgrade.

      There are some tables that are defined in code. (e.g. system.local)

      When v3 sstable schema for these tables detects:

      • a column in the sstable schema that is not in the data schema it creates a deleted column in the data schema.
      • a column in the data schema that is not in the sstable schema it throws an exception.

       

      There are two basic approaches to solve this:

      • rewrite the data so that the additional column is removed.  This is an expensive process.
      • rework the code so that columns in the data but not in the table are ignored for this class of tables (statically defined in code).

      Attachments

        Issue Links

        Activity

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

          People

            claude Claude Warren Assign to me
            claude Claude Warren
            Claude Warren

            Dates

              Created:
              Updated:

              Slack

                Issue deployment