Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-32589

FULL_NODUP mode for binlog_row_image

Details

    Description

      With FULL_NODUP mode, all columns are included in before image, but only updated columns are included in after image for UPDATE. While all columns are included in the after image for INSERT.

      FULL_NODUP is for replacing FULL mode. It includes all data of the before and after image as FULL mode, but it uses less storage, especially in the case that only a few columns are updated.

      This Jira is to track the contribution by Alibaba (https://github.com/MariaDB/server/pull/2803)

      (Note that originally the MDEV was referring to the original Alibaba option, FULL_DIFFERENT. This was changed to FULL_NODUP to reflect the option implemented in MariaDB).

      Attachments

        Issue Links

          Activity

            Transition Time In Source Status Execution Times
            Sergei Golubchik made transition -
            Open In Progress
            8d 3h 35m 1
            Sergei Golubchik made transition -
            In Progress In Review
            6s 1
            Andrei Elkin made transition -
            In Review Stalled
            17d 23h 36m 1
            Andrew Hutchings (Inactive) made transition -
            Stalled In Testing
            1d 17h 34m 1
            Ramesh Sivaraman made transition -
            In Testing Stalled
            54d 7h 43m 1
            Andrew Hutchings (Inactive) made transition -
            Stalled Closed
            1d 20h 15m 1

            People

              TheLinuxJedi Andrew Hutchings (Inactive)
              TheLinuxJedi Andrew Hutchings (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.