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

the lost of "BEGIN" in mariadb server's binlog result in our lots of projects not working

Details

    Description

      we have developed lots of projects based on mysql/mariadb Binlog, but in newest version of mariadb server, the BEGIN event have lost in row based binlog, which result in our projects not working at all. but in Oracle's mysql, the BEGIN event still been there.

      what happened on Mariadb? is it a bug? this issue is very critical to our projects, if it can not included in, we have only one choice: choose to use Oracle/MySQL.

      in attachments, WechatIMG230.jpeg is Mariadb, the BEGIN is included to GTID event, so there have lost the BEGIN event info, such as thread id..., detailed info as 1523853247199.jpg, WechatIMG228.jpeg is Oracle/MySQL, the BEGIN is still an alone event, I can read the thread id from it, detailed info as 1523853121489.jpg

      Attachments

        1. 1523853121489.jpg
          1523853121489.jpg
          215 kB
        2. 1523853247199.jpg
          1523853247199.jpg
          194 kB
        3. WechatIMG228.jpeg
          WechatIMG228.jpeg
          219 kB
        4. WechatIMG230.jpeg
          WechatIMG230.jpeg
          94 kB

        Issue Links

          duplicates

          New Feature - A new feature of the product, which has yet to be developed. MDEV-7850 Extend GTID Binlog Events with Thread Id

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. MDEV-20925 Add thread id and Transaction length data to gtid_log_event

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          is part of

          Task - A task that needs to be done. MDEV-20925 Add thread id and Transaction length data to gtid_log_event

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            doathink doathink added a comment -

            how about this problem?

            doathink doathink added a comment - how about this problem?
            serg Sergei Golubchik added a comment -

            Unfortunately, this bug report has missed the 10.2.17 release, so now there may be no activity here until closer to the 10.2.18 release. See https://jira.mariadb.org/ for the planned release dates.

            serg Sergei Golubchik added a comment - Unfortunately, this bug report has missed the 10.2.17 release, so now there may be no activity here until closer to the 10.2.18 release. See https://jira.mariadb.org/ for the planned release dates.
            doathink doathink added a comment -

            OK，I will continue to pay attention，thanks

            doathink doathink added a comment - OK，I will continue to pay attention，thanks
            Elkin Andrei Elkin added a comment -

            doathink, thanks for the report!

            In MariaDB the transaction start event in binlog is Gtid_log_event, that carries out transaction identification
            and its BEGIN Query_log_event. Indeed thread_id info is missed out in our Gtid_log_event printout and this
            can be fixed quickly. I wonder if this action alone would be satisfactory for you? It is also possible to print Gtid_log_event out
            in the mysql way, sort of masquerading them. But that's even less difficult to do with help of a small filter script piping in
            mysqlbinlog output.

            Could you please suggest your preference?

            Regards,

            Andrei Elkin

            Elkin Andrei Elkin added a comment - doathink , thanks for the report! In MariaDB the transaction start event in binlog is Gtid_log_event, that carries out transaction identification and its BEGIN Query_log_event. Indeed thread_id info is missed out in our Gtid_log_event printout and this can be fixed quickly. I wonder if this action alone would be satisfactory for you? It is also possible to print Gtid_log_event out in the mysql way, sort of masquerading them. But that's even less difficult to do with help of a small filter script piping in mysqlbinlog output. Could you please suggest your preference? Regards, Andrei Elkin
            doathink doathink added a comment -

            thanks for Andrei Elkin very much.
            I only need the BEGIN event, which include the thread_id, it enough. it would be satisfactory for me very good.

            thanks again.

            doathink doathink added a comment - thanks for Andrei Elkin very much. I only need the BEGIN event, which include the thread_id, it enough. it would be satisfactory for me very good. thanks again.
            Elkin Andrei Elkin added a comment -

            I new thread_id can be added to Gtid_log_event, and as it's the user visible change I think it may go only to the current development branch of 10.5.

            Elkin Andrei Elkin added a comment - I new thread_id can be added to Gtid_log_event, and as it's the user visible change I think it may go only to the current development branch of 10.5.
            Elkin Andrei Elkin added a comment -

            MDEV-20925 generalizes this case and there's been actual work on it, so this one can
            be closed as a dup.

            Elkin Andrei Elkin added a comment - MDEV-20925 generalizes this case and there's been actual work on it, so this one can be closed as a dup.
            sachin.setiya.007 Sachin Setiya (Inactive) added a comment -

            MDEV-20925 is closed without fixing, So I am opening this issue

            sachin.setiya.007 Sachin Setiya (Inactive) added a comment - MDEV-20925 is closed without fixing, So I am opening this issue

            People

              sujatha.sivakumar Sujatha Sivakumar (Inactive)
              doathink doathink
              Votes:
              0 Vote for this issue
              Watchers:
              5 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.