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

Undefined outcome on schemarouter query conflict

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.6
    • Fix Version/s: 2.1.7
    • Component/s: schemarouter
    • Labels:
      None

      Description

      When a query targets databases that are on two different servers, the schemarouter will route it to the first server that is parsed. This causes somewhat unexpected behavior when a better alternative is to route it to the server which contains the current active database. The current database is a lot easier to control compared to the order the database appear in the query itself.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              markus makela markus makela
              Reporter:
              markus makela markus makela
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration