[MXS-2074] Handle prepared statements in NamedServerFilter Created: 2018-09-27 Updated: 2023-05-08 Resolved: 2021-10-27 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | namedserverfilter |
| Affects Version/s: | 2.2.14 |
| Fix Version/s: | 6.2.0 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Chris Calender (Inactive) | Assignee: | Esa Korhonen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | MXS-SPRINT-142, MXS-SPRINT-143 |
| Description |
|
This is a request to allow NamedServerFilter to be able to route prepared statements to a specific server based on user and/or host. This currently works fine for SELECT, INSERT, UPDATE, DELETE, but does not work for prepared statements. Per Markus, "the namedserverfilter will add a hint for the preparation but the execution of the prepared statement will not get a hint". We see this when running sysbench against the NamedServerFilter, as the queries are not routed, unless you specify the --db-ps-mode=disable option. |
| Comments |
| Comment by Johan Wikman [ 2018-11-19 ] |
|
We are likely to change the namedserverfilter into a router that is capable of routing incoming requests, depending on their characteristics, to different services. At the same time we will ensure that prepared statements are handled properly. |