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

remove support for 5.1- replication events

Details

    Description

      In particular:
      "binglog version 1" — for 3.23 events
      *_PRE_GA_* row events — 5.1.0 to 5.1.15, "pre GA" 5.1
      sql/*_old.* — same
      may be more

      Attachments

        Issue Links

          Activity

            serg Sergei Golubchik created issue -
            serg Sergei Golubchik made changes -
            Field Original Value New Value
            Assignee Andrei Elkin [ elkin ] Sergei Golubchik [ serg ]
            serg Sergei Golubchik made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            serg Sergei Golubchik made changes -
            Status In Progress [ 3 ] Stalled [ 10000 ]
            serg Sergei Golubchik made changes -
            Status Stalled [ 10000 ] In Testing [ 10301 ]
            serg Sergei Golubchik made changes -
            Status In Testing [ 10301 ] Stalled [ 10000 ]
            serg Sergei Golubchik made changes -
            Assignee Sergei Golubchik [ serg ] Andrei Elkin [ elkin ]
            Status Stalled [ 10000 ] In Review [ 10002 ]
            Elkin Andrei Elkin added a comment -

            The changes look good, yet they are not complete. I created bb-10.11-MDEV-30128-andrei branch with a commit on the top of this one. Could you please review and incorporate (or I could do the latter)?

            Elkin Andrei Elkin added a comment - The changes look good, yet they are not complete. I created bb-10.11-MDEV-30128-andrei branch with a commit on the top of this one. Could you please review and incorporate (or I could do the latter)?
            Elkin Andrei Elkin made changes -
            Assignee Andrei Elkin [ elkin ] Sergei Golubchik [ serg ]
            Status In Review [ 10002 ] Stalled [ 10000 ]

            Thanks. I went one step further and removed Load_log_event completely

            serg Sergei Golubchik added a comment - Thanks. I went one step further and removed Load_log_event completely
            Elkin Andrei Elkin added a comment -

            serg, I did not dare to remove the veteran .
            But also have to proceed on to clean out of remains of START_EVENT_V3, the commit is here
            421f0078161..1c086060922 HEAD -> bb-10.11-MDEV-30128-andrei.

            Elkin Andrei Elkin added a comment - serg , I did not dare to remove the veteran . But also have to proceed on to clean out of remains of START_EVENT_V3, the commit is here 421f0078161..1c086060922 HEAD -> bb-10.11-MDEV-30128-andrei .
            serg Sergei Golubchik made changes -
            Status Stalled [ 10000 ] In Testing [ 10301 ]
            angelique.sklavounos Angelique Sklavounos (Inactive) made changes -
            Assignee Sergei Golubchik [ serg ] Angelique Sklavounos [ JIRAUSER50741 ]

            Testing with 0529784d3 and 3340d2c67012 looked okay.

            angelique.sklavounos Angelique Sklavounos (Inactive) added a comment - Testing with 0529784d3 and 3340d2c67012 looked okay.
            angelique.sklavounos Angelique Sklavounos (Inactive) made changes -
            Assignee Angelique Sklavounos [ JIRAUSER50741 ] Sergei Golubchik [ serg ]
            Status In Testing [ 10301 ] Stalled [ 10000 ]
            serg Sergei Golubchik made changes -
            Fix Version/s 11.0.1 [ 28548 ]
            Fix Version/s 11.0 [ 28320 ]
            Resolution Fixed [ 1 ]
            Status Stalled [ 10000 ] Closed [ 6 ]
            ralf.gebhardt Ralf Gebhardt made changes -
            Labels Preview_11.0
            marko Marko Mäkelä made changes -

            People

              serg Sergei Golubchik
              serg Sergei Golubchik
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.