[MXS-1379] Undefined outcome on schemarouter query conflict Created: 2017-08-30 Updated: 2017-09-01 Resolved: 2017-09-01 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | schemarouter |
| Affects Version/s: | 2.1.6 |
| Fix Version/s: | 2.1.7 |
| Type: | Bug | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| 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. |