Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.4.12
-
CentOS Linux release 7.7.1908 (Core)
Description
echo -e 'OS@'$(cat /etc/redhat-release)'\nMariaDB Version@'$(mysql -V)'\nDefault plugin-dir@'$(mysql --help | grep -Pi '^plugin\-dir' | perl -pe 's/[\s]+\(/@(/g' | cut -d '@' -f 2)'\nManual plugin-dir@'$(mysql --plugin-dir=/usr/lib64/mysql/plugin/ --help | grep -Pi '^plugin\-dir' | perl -pe 's/[\s]+/@/g' | cut -d '@' -f 2) | column -s '@' -t |
OS CentOS Linux release 7.7.1908 (Core)
|
MariaDB Version mysql Ver 15.1 Distrib 10.4.12-MariaDB, for Linux (x86_64) using readline 5.1 |
Default plugin-dir (No default value) |
Manual plugin-dir /usr/lib64/mysql/plugin/ |
As per MDEV-19807, this should be defaulting to the plugin directory installed by the RPM by default. Therefore, the behavior of plugin-dir not having an assigned value unless it is configured manually (ala via mysql --plugin-dir=) seems incorrect and may need to be addressed.
If a default value is set though, then mysql --help is outputting incorrect information as a path is set but (No default value) is being output.
The use-case I investigated this for involved installing MariaDB-client on a Linux VM without installing MariaDB-server or anything else, simulating the experience of a client connecting to a remote MariaDB server. Here is some additional context on the RPMs I had installed-
yum list installed | grep -i MariaDB |
MariaDB-client.x86_64 10.4.12-1.el7.centos @mariadb-main
|
MariaDB-common.x86_64 10.4.12-1.el7.centos @mariadb-main
|
MariaDB-compat.x86_64 10.4.12-1.el7.centos @mariadb-main
|