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

Ensure replication actions are idempotent if any series of events are applied again.

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.1.0
    • 3.0.0
    • Hive, repl

    Description

      Some of the events(ALTER, RENAME, TRUNCATE) are not idempotent and hence leads to failure of REPL LOAD if applied twice or applied on an object which is latest than current event. For example, if TRUNCATE is applied on a table which is already dropped will fail instead of noop.
      Also, need to consider the scenario where the object is missing while applying an event. For example, if RENAME_TABLE event is applied on target where the old table is missing should validate if table should be recreated or should treat the event as noop. This can be done by verifying the DB level last repl ID against the current event ID.

      Attachments

        1. HIVE-16785.01.patch
          49 kB
          Sankar Hariappan
        2. HIVE-16785.02.patch
          59 kB
          Sankar Hariappan
        3. HIVE-16785.03.patch
          63 kB
          Sankar Hariappan
        4. HIVE-16785.04.patch
          66 kB
          Sankar Hariappan
        5. HIVE-16785.05.patch
          71 kB
          Sankar Hariappan

        Issue Links

          Activity

            People

              sankarh Sankar Hariappan
              sankarh Sankar Hariappan
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: