Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-2750

COM_STMT_EXECUTE in transaction get unexpected result

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.2.21, 2.3.13
    • 2.5.0
    • readwritesplit
    • None
    • MXS-SPRINT-99

    Description

      We fix MX-2521 by routing the execute stmts which n_params > 0 and no metadata to previous node, but it not works with transaction,
      For example:

      prepare;
      		 
      execute; // to ro1 with metadata
      		 
      execute; // to ro1 with without metadata
      		 
      begin;
      		 
      execute; //  to master without metadata;
      		 
      commit;

      Suggestion:
      1. Record metadata in first execution;
      2. Add metadata to the following execution ( maybe every backend just add once)

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. MXS-2521 COM_STMT_EXECUTE maybe return empty result

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MXS-3565 COM_STMT_EXECUTE target selection is too restrictive when no metadata is provided

          • Major - Major loss of function.
          • Closed

          Activity

            People

              markus makela markus makela
              huangyouqian huangyouqian
              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.