Uploaded image for project: 'Hive'
  1. Hive
  2. HIVE-14841 Replication - Phase 2
  3. HIVE-16642

New Events created as part of replv2 potentially break replv1

Log workAgile BoardRank to TopRank to BottomBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersConvert to IssueMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 3.0.0
    • repl
    • None

    Description

      We have a couple of new events introduced, such as {CREATE,DROP}{INDEX,FUNCTION} since the introduction of replv1, but those which do not have a replv1 ReplicationTask associated with them.

      Thus, for users like Falcon, we potentially wind up throwing a IllegalStateException if replv1 based HiveDR is running on a cluster with these updated events.

      Thus, we should be more graceful when encountering them, returning a NoopReplicationTask equivalent that they can make use of, or ignore, for such newer events.

      In addition, we should add additional test cases so that we track whether or not the creation of these events leads to any backward incompatibility we introduce. To this end, if any of the events should change so that we introduce a backward incompatibility, we should have these tests fail, and alert us to that possibility.

      Attachments

        1. HIVE-16642.1.patch
          23 kB
          Sushanth Sowmyan
        2. HIVE-16642.2.patch
          22 kB
          Sushanth Sowmyan
        3. HIVE-16642.3.patch
          22 kB
          Sushanth Sowmyan

        Activity

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

          People

            sushanth Sushanth Sowmyan Assign to me
            sushanth Sushanth Sowmyan
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment