[MDEV-18093] PLUGIN UNUSABLE does not exist Created: 2018-12-27  Updated: 2018-12-28  Resolved: 2018-12-28

Status: Closed
Project: MariaDB Server
Component/s: Plugins
Affects Version/s: 10.0, 10.4
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Ian Gilfillan Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: need_feedback


 Description   

Plugin name is returned as 'UNUSABLE' in the below example from 10.4.1:

INSTALL PLUGIN IF NOT EXISTS example SONAME 'ha_example';
Query OK, 0 rows affected (0.104 sec)
 
UNINSTALL SONAME IF EXISTS 'ha_example';
Query OK, 0 rows affected, 1 warning (0.095 sec)
 
SHOW WARNINGS;
+-------+------+--------------------------------+
| Level | Code | Message                        |
+-------+------+--------------------------------+
| Note  | 1305 | PLUGIN UNUSABLE does not exist |
+-------+------+--------------------------------+
1 row in set (0.000 sec)
 
UNINSTALL SONAME IF EXISTS 'ha_example';
Query OK, 0 rows affected, 1 warning (0.000 sec)
 
SHOW WARNINGS;
+-------+------+-------------------------------------+
| Level | Code | Message                             |
+-------+------+-------------------------------------+
| Note  | 1305 | SONAME ha_example.so does not exist |
+-------+------+-------------------------------------+

The same occurs if the IF [NOT] EXISTS clauses are omitted, and in 10.0.



 Comments   
Comment by Ian Gilfillan [ 2018-12-27 ]

See discussion at https://github.com/MariaDB/server/pull/757

Comment by Elena Stepanova [ 2018-12-28 ]

I think it makes sense. There are two plugins in ha_example.so, EXAMPLE and UNUSABLE.
INSTALL PLUGIN example SONAME 'ha_example' only installs the example plugin, but UNINSTALL SONAME 'ha_example' attempts to uninstall both. It finds and uninstalls the previously installed EXAMPLE, but can't find UNUSABLE and complains about it.

Or do I misunderstand the nature of the report?

Comment by Ian Gilfillan [ 2018-12-28 ]

Thanks, it seems to make sense. I wasn't aware that UNUSABLE was the name of a plugin when I posted, so it seemed like a generic naming error.

Generated at Thu Feb 08 08:41:27 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.