[MDEV-31705] Upgrade MariaDB clients with --catalog Created: 2023-07-15  Updated: 2023-12-22

Status: Open
Project: MariaDB Server
Component/s: Scripts & Clients
Fix Version/s: 11.5

Type: Task Priority: Major
Reporter: Michael Widenius Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
PartOf
is part of MDEV-31542 Add multi-tenancy catalogs to MariaDB Stalled

 Description   

The 'mariadb' client has already support for --catalog

We should add the --catalog option to all other MariaDB tools using the
mysql_optionsv(mysql, MARIADB_OPT_CATALOG, catalog);
call
(Note that mysql.cc has code to work with client libraries that does not support the
MARIADB_OPT_CATALOG call. This is there only for developers wanting to know how to
use catalogs with older client libraries and should not be copied to our other clients).

Clients to be upgrade:

  • mariadb-admin
  • mariadb-show
  • mariadb-binlog
  • mariadb-dump
  • mariadb-slap
  • mariadb-check
  • mariadb-import
  • mariadb-test
  • mariadb-conv
  • mariadb-plugin
  • mariadb-upgrade
  • Needs to be run for all catalogs
  • We also need to change 'mysql_fix_privilege_tables' to only fix the
    tables that should exists in the catalog:
  • 'def' has all tables
  • all-other, only the catalog specific tables.

 Comments   
Comment by markus makela [ 2023-09-22 ]

If possible, please update either the Jira items or the KB with the planned and/or implemented protocol level changes. This'll help "third parties" like MaxScale implement it in time for the 11.4 release.

From what I heard from TheLinuxJedi the plan is to use a dot as a separator and a new capability bit.

Generated at Thu Feb 08 10:25:51 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.