[MXS-341] MaxScale won't work on MySQL 5.7 due to missing password column in mysql.user table Created: 2015-08-29 Updated: 2017-12-01 Resolved: 2015-11-12 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | 1.2.1 |
| Fix Version/s: | 1.3.0 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Simon J Mudd | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
While MySQL 5.7 is not GA (and therefore officially released yet) it is expected to come out in the next couple of months. The current release is marked as rc "release candidate" which seems to indicate this. One of the changes in MySQL 5.7 are grant privileges and related to that are changes to the mysql.user table. The password column has been removed and "replaced" by the authentication_string column. Given the MaxScale code currently explicitly looks at the password column any attempt to do this on a MySQL 5.7 server is going to fail. This JIRA ticket is really to record this issue so it can be dealt with in due course and before 5.7 goes GA when this will affect users of MaxScale. This improvement request is to adjust MaxScale so it will work with MySQL 5.7. |
| Comments |
| Comment by Simon J Mudd [ 2015-08-29 ] |
|
As far as I can tell this is related to code in MaxScale/server/core/dbusers.c. |
| Comment by Simon J Mudd [ 2015-08-29 ] |
|
I notice you have as priorities: Minor and Major (amongst others). |
| Comment by markus makela [ 2015-11-12 ] |
|
MaxScale now supports the 5.7 layout of the mysql.user table. |