Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
2.3.12, 2.4.2
-
None
-
MXS-SPRINT-96
Description
When connecting through maxscale custom connection attributes are not passed through.
When e.g. connecting directly with the command line client, we can see the following connection attributes being set by the client:
SELECT *
|
FROM performance_schema.session_connect_attrs
|
WHERE processlist_id = connection_id();
|
 |
+----------------+-----------------+------------+------------------+
|
| PROCESSLIST_ID | ATTR_NAME | ATTR_VALUE | ORDINAL_POSITION |
|
+----------------+-----------------+------------+------------------+
|
| 13 | _os | Linux | 0 |
|
| 13 | _client_name | libmariadb | 1 |
|
| 13 | _pid | 1889 | 2 |
|
| 13 | _client_version | 3.0.10 | 3 |
|
| 13 | _platform | x86_64 | 4 |
|
| 13 | program_name | mysql | 5 |
|
| 13 | _server_host | node-1 | 6 |
|
+----------------+-----------------+------------+------------------+
|
When connecting through maxscale, none of the connections attributes are visible in the PERFORMANCE_SCHEMA.SESSION_CONNECT_ATTRS table ...
See also:
https://mariadb.com/kb/en/library/mysql_optionsv/#connection-attribute-options
https://mariadb.com/kb/en/library/performance-schema-session_connect_attrs-table/