[debian-mysql] Bug#773727: Bug#773727: Bug#773727: mariadb-server-10.0: Mroonga & TokuDB plugins missing

[Arnaud Fontaine]

Hi Otto,

Otto Kekäläinen <otto at seravo.fi> writes:

> After thinking about it for a while, I am starting to think that the
> best policy would be to _not_ load bundled plugins by default if they
> are not compulsory for the server to run. It is better to keep the
> server lean and sleek, and let the user activate extra plugins if they
> need them.

Indeed.

> We could however facilitate the activation of plugins by shipping them
> in separate packages (e.g. like mariadb-connect-engine-10.0 is now) so
> all the user needs to do is run 'apt-get install
> mariadb-mroonga-search-10.0' or similar. These packages could then
> contain the plugin files itself, any configuration that need to be
> dropped in /etc/mysql/conf.d/ and potentially also install/remove
> scripts.
>
> What do you think, does this sound like a good policy?

Considering that  it is currently  inconsistent (eg CONNECT  and OQGRAPH
engines are in  separate packages but Mroonga and Spider  are not), then
it would be good to address  this inconsistency. Excluding the ones that
are already packaged separately (namely OQGRAPH and CONNECT engines):

> SELECT PLUGIN_NAME, PLUGIN_LIBRARY FROM information_schema.ALL_PLUGINS WHERE PLUGIN_LIBRARY IS NOT NULL GROUP BY PLUGIN_LIBRARY;
+----------------------+------------------------+
| PLUGIN_NAME          | PLUGIN_LIBRARY         |
+----------------------+------------------------+
| pam                  | auth_pam.so            |
| unix_socket          | auth_socket.so         |
| handlersocket        | handlersocket.so       |
| InnoDB               | ha_innodb.so           |
| SEQUENCE             | ha_sequence.so         |
| SPHINX               | ha_sphinx.so           |
| SPIDER               | ha_spider.so           |
| LOCALES              | locales.so             |
| METADATA_LOCK_INFO   | metadata_lock_info.so  |
| QUERY_CACHE_INFO     | query_cache_info.so    |
| QUERY_RESPONSE_TIME  | query_response_time.so |
| rpl_semi_sync_master | semisync_master.so     |
| rpl_semi_sync_slave  | semisync_slave.so      |
| SERVER_AUDIT         | server_audit.so        |
| SQL_ERROR_LOG        | sql_errlog.so          |
+----------------------+------------------------+
15 rows in set (0.01 sec)

So, here are several solutions I could think of: 

  1. Create  one package  per plugin  as you  suggested, but  this would
     create many (some of them really small) packages though. Or perhaps
     one package containing several plugins,  because some of them, such
     as query_cache_info, are really small?

  2. Keep  it as it  is, eg let users  manage plugins by  themselves and
     thus not load any plugin by  default. This is not really convenient
     as  some plugins  requires  more than  a plugin-load  configuration
     option (mroonga does requires "CREATE FUNCTION" for example).

  3. Keep  all the plugins  in mariadb-server-10.0 but let  users choose
     which plugins to install (and then run necessary scripts) through a
     debconf menu.

What do you think?

Cheers,
-- 
Arnaud Fontaine
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20150210/6db10007/attachment-0001.sig>