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

human-readable XA RECOVER

Details

    • Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.3.3
    • XA
    • None
    • 10.1.30

    Description

      XA RECOVER prints data in binary, because that format — raw XIDs — is most useful for the transaction coordinator.

      But occasionally, a human intervention is necessary. For this use case it would be convenient if XA RECOVER could return XID in some format that can be directly copied into XA COMMIT or XA ROLLBACK.

      Also, mysql command line client has a --binary-as-hex option, but it does not work for XA RECOVER. It should be fixed, if possible.

      MySQL has the command XA RECOVER CONVERT XID that returns the value of XID in hex. But it cannot be directly copied into XA COMMIT or XA ROLLBACK.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14595 Add "CONVERT" option to "XA RECOVER"

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14913 Document human-readable XA RECOVER

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14922 XA RECOVER FORMAT='SQL' requires quotes while XA RECOVER FORMAT=RAW does not

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Confirmed
          links to

          Web Link Bug #87526 The output of 'XA recover convert xid' is not useful

          Web Link lp:1712649 The output of 'XA recover convert xid' is not useful

          Activity

            Ascending order - Click to sort in descending order
            serg Sergei Golubchik created issue -
            serg Sergei Golubchik made changes -
            Field Original Value New Value
            serg Sergei Golubchik made changes -
            serg Sergei Golubchik made changes -
            Description {{XA RECOVER}} prints data in binary, because that format — raw XIDs — is most useful for the transaction coordinator.

            But occasionally, a human intervention is necessary. For this use case it would be convenient if {{XA RECOVER}} could return XID in some format that can be directly copied into {{XA COMMIT}} or {{XA ROLLBACK}}.

            Also, {{mysql}} command line client has a {{--binary-as-hex}} option, but it does not work for {{XA RECOVER}}. It should be fixed, if possible.             		{{XA RECOVER}} prints data in binary, because that format — raw XIDs — is most useful for the transaction coordinator.

            But occasionally, a human intervention is necessary. For this use case it would be convenient if {{XA RECOVER}} could return XID in some format that can be directly copied into {{XA COMMIT}} or {{XA ROLLBACK}}.

            Also, {{mysql}} command line client has a {{--binary-as-hex}} option, but it does not work for {{XA RECOVER}}. It should be fixed, if possible.

            MySQL has the command {{XA RECOVER CONVERT XID}} that returns the value of XID in hex. But it cannot be directly copied into {{XA COMMIT}} or {{XA ROLLBACK}}.
            serg Sergei Golubchik made changes -
            holyfoot Alexey Botchkov made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            holyfoot Alexey Botchkov added a comment -

            Patch proposal:
            http://lists.askmonty.org/pipermail/commits/2017-December/011705.html

            holyfoot Alexey Botchkov added a comment - Patch proposal: http://lists.askmonty.org/pipermail/commits/2017-December/011705.html
            holyfoot Alexey Botchkov made changes -
            Assignee Alexey Botchkov [ holyfoot ] Sergei Golubchik [ serg ]
            Status In Progress [ 3 ] In Review [ 10002 ]
            holyfoot Alexey Botchkov added a comment -

            new patch
            http://lists.askmonty.org/pipermail/commits/2017-December/011729.html

            holyfoot Alexey Botchkov added a comment - new patch http://lists.askmonty.org/pipermail/commits/2017-December/011729.html
            serg Sergei Golubchik made changes -
            Sprint 10.1.30 [ 215 ]
            serg Sergei Golubchik made changes -
            Assignee Sergei Golubchik [ serg ] Alexey Botchkov [ holyfoot ]
            Status In Review [ 10002 ] Stalled [ 10000 ]
            holyfoot Alexey Botchkov added a comment -

            http://lists.askmonty.org/pipermail/commits/2017-December/011735.html

            holyfoot Alexey Botchkov added a comment - http://lists.askmonty.org/pipermail/commits/2017-December/011735.html
            holyfoot Alexey Botchkov made changes -
            issue.field.resolutiondate 2017-12-17 22:24:23.0 2017-12-17 22:24:23.054
            holyfoot Alexey Botchkov made changes -
            Fix Version/s 10.2.12 [ 22810 ]
            Fix Version/s 10.2 [ 14601 ]
            Resolution Fixed [ 1 ]
            Status Stalled [ 10000 ] Closed [ 6 ]
            serg Sergei Golubchik made changes -
            Fix Version/s 10.3.3 [ 22644 ]
            Fix Version/s 10.2.12 [ 22810 ]
            greenman Ian Gilfillan made changes -
            greenman Ian Gilfillan made changes -
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 84322 ] MariaDB v4 [ 133414 ]
            mariadb-jira-automation Jira Automation (IT) made changes -
            Zendesk Related Tickets 117804 165803

            People

              holyfoot Alexey Botchkov
              serg Sergei Golubchik
              Votes:
              1 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.