[MDEV-26307] multi-source-replication support mysql syntax(for channel) - Jira

woqutech.com created issue - 2021-08-05 02:48

woqutech.com made changes - 2021-08-05 02:51

Field	Original Value	New Value
Description	# backugroud MariaDB and MySQL both implement the multi-source replication, but their usage and internal implementation are different. In order to facilitate the migration of MySQL users to MariaDB, we want to support MySQL syntax # describe * For CHANGE MASTER/FLUSH RELAY LOG/RESET SLAVE/SHOW RELAY LOG EVENT/SHOW SLAVE STATUS/START SLAVE/STOP SLAVE commands support FOR CHANNEL syntax * "FOR CHANNEL" is just an alias for connection\_name, does not change the original implementation, all behaviors are consistent with MariaDB, so some operations are not compatible with MySQL, For example: (MySQL) When a replica has multiple channels and a FOR CHANNEL channel option is not specified, a valid statement generally acts on all available channels, with some specific exceptions. (MariaDB) You specify which primary connection you want to work with by either specifying the connection name in the command or setting default_master_connection to the connection you want to work with * The channel name supports up to 64 bytes, and is not case sensitive * The connection name and for channel syntax cannot be used at the same time, otherwise an error will be reported * MariaDB syntax is highly compatible with MySQL, so there is no special SQL_MODE set like Oracle/SQL Server and other databases, FOR CHANNEL is not affected by SQL_MODE # new syntax for MariaDB ## CHANGE MASTER {code:java} CHANGE MASTER ['connection_name'] TO master_def [, master_def] ... [FOR CHANNEL 'channel_name'] {code} ## FLUSH RELAY LOG {code:java} FLUSH RELAY LOGS ['connection_name' \| FOR CHANNEL 'channel_name'] {code} ## RESET SLAVE {code:java} RESET SLAVE ['connection_name'] [ALL] [FOR CHANNEL 'channel_name'] {code} ## SHOW RELAY LOG EVENT {code:java} SHOW RELAYLOG ['connection_name'] EVENTS [IN 'log_name'] [FROM pos] [LIMIT [offset,] row_count] [ FOR CHANNEL 'channel_name'] {code} ## SHOW SLAVE STATUS {code:java} SHOW SLAVE ['connection_name'] STATUS [FOR CHANNEL 'channel_name'] {code} ## START SLAVE {code:java} START SLAVE ['connection_name'] [thread_type [, thread_type] ... ] [FOR CHANNEL 'channel_name'] {code} ## STOP SLAVE {code:java} STOP SLAVE ['connection_name'] [thread_type [, thread_type] ... ] [FOR CHANNEL 'channel_name'] {code}	h1. backugroud MariaDB and MySQL both implement the multi-source replication, but their usage and internal implementation are different. In order to facilitate the migration of MySQL users to MariaDB, we want to support MySQL syntax h1. describe * For CHANGE MASTER/FLUSH RELAY LOG/RESET SLAVE/SHOW RELAY LOG EVENT/SHOW SLAVE STATUS/START SLAVE/STOP SLAVE commands support FOR CHANNEL syntax * "FOR CHANNEL" is just an alias for connection\_name, does not change the original implementation, all behaviors are consistent with MariaDB, so some operations are not compatible with MySQL, For example: (MySQL) When a replica has multiple channels and a FOR CHANNEL channel option is not specified, a valid statement generally acts on all available channels, with some specific exceptions. (MariaDB) You specify which primary connection you want to work with by either specifying the connection name in the command or setting default_master_connection to the connection you want to work with * The channel name supports up to 64 bytes, and is not case sensitive * The connection name and for channel syntax cannot be used at the same time, otherwise an error will be reported * MariaDB syntax is highly compatible with MySQL, so there is no special SQL_MODE set like Oracle/SQL Server and other databases, FOR CHANNEL is not affected by SQL_MODE h1. new syntax for MariaDB h2. CHANGE MASTER {code:java} CHANGE MASTER ['connection_name'] TO master_def [, master_def] ... [FOR CHANNEL 'channel_name'] {code} h2. FLUSH RELAY LOG {code:java} FLUSH RELAY LOGS ['connection_name' \| FOR CHANNEL 'channel_name'] {code} h2. RESET SLAVE {code:java} RESET SLAVE ['connection_name'] [ALL] [FOR CHANNEL 'channel_name'] {code} h2. SHOW RELAY LOG EVENT {code:java} SHOW RELAYLOG ['connection_name'] EVENTS [IN 'log_name'] [FROM pos] [LIMIT [offset,] row_count] [ FOR CHANNEL 'channel_name'] {code} h2. SHOW SLAVE STATUS {code:java} SHOW SLAVE ['connection_name'] STATUS [FOR CHANNEL 'channel_name'] {code} h2. START SLAVE {code:java} START SLAVE ['connection_name'] [thread_type [, thread_type] ... ] [FOR CHANNEL 'channel_name'] {code} h2. STOP SLAVE {code:java} STOP SLAVE ['connection_name'] [thread_type [, thread_type] ... ] [FOR CHANNEL 'channel_name'] {code}

woqutech.com made changes - 2021-08-14 07:11

Description

h1. backugroud
MariaDB and MySQL both implement the multi-source replication, but their usage and internal implementation are different. In order to facilitate the migration of MySQL users to MariaDB, we want to support MySQL syntax

h1. describe
* For CHANGE MASTER/FLUSH RELAY LOG/RESET SLAVE/SHOW RELAY LOG EVENT/SHOW SLAVE STATUS/START SLAVE/STOP SLAVE commands support FOR CHANNEL syntax
* "FOR CHANNEL" is just an alias for connection\_name, does not change the original implementation, all behaviors are consistent with MariaDB, so some operations are not compatible with MySQL, For example:
(MySQL) When a replica has multiple channels and a FOR CHANNEL channel option is not specified, a valid statement generally acts on all available channels, with some specific exceptions.
(MariaDB) You specify which primary connection you want to work with by either specifying the connection name in the command or setting default_master_connection to the connection you want to work with
* The channel name supports up to 64 bytes, and is not case sensitive
* The connection name and for channel syntax cannot be used at the same time, otherwise an error will be reported
* MariaDB syntax is highly compatible with MySQL, so there is no special SQL_MODE set like Oracle/SQL Server and other databases, FOR CHANNEL is not affected by SQL_MODE

h1. new syntax for MariaDB
h2. CHANGE MASTER
{code:java}
CHANGE MASTER ['connection_name'] TO master_def [, master_def] ... [FOR CHANNEL 'channel_name']
{code}

h2. FLUSH RELAY LOG

{code:java}
FLUSH RELAY LOGS ['connection_name' | FOR CHANNEL 'channel_name']
{code}

h2. RESET SLAVE

{code:java}
RESET SLAVE ['connection_name'] [ALL] [FOR CHANNEL 'channel_name']
{code}

h2. SHOW RELAY LOG EVENT

{code:java}
SHOW RELAYLOG ['connection_name'] EVENTS [IN 'log_name'] [FROM pos] [LIMIT [offset,] row_count] [ FOR CHANNEL 'channel_name']
{code}

h2. SHOW SLAVE STATUS

{code:java}
SHOW SLAVE ['connection_name'] STATUS [FOR CHANNEL 'channel_name']
{code}

h2. START SLAVE

{code:java}
START SLAVE ['connection_name'] [thread_type [, thread_type] ... ] [FOR CHANNEL 'channel_name']
{code}

h2. STOP SLAVE

{code:java}
STOP SLAVE ['connection_name'] [thread_type [, thread_type] ... ] [FOR CHANNEL 'channel_name']
{code}

_emphasized text_h1. backugroud
MariaDB and MySQL both implement the multi-source replication, but their usage and internal implementation are different. In order to facilitate the migration of MySQL users to MariaDB, we want to support MySQL syntax

h1. describe
* For CHANGE MASTER/FLUSH RELAY LOG/RESET SLAVE/SHOW RELAY LOG EVENT/SHOW SLAVE STATUS/START SLAVE/STOP SLAVE commands support FOR CHANNEL syntax
* "FOR CHANNEL" is just an alias for connection\_name, does not change the original implementation, all behaviors are consistent with MariaDB, so some operations are not compatible with MySQL, For example:
(MySQL) When a replica has multiple channels and a FOR CHANNEL channel option is not specified, a valid statement generally acts on all available channels, with some specific exceptions.
(MariaDB) You specify which primary connection you want to work with by either specifying the connection name in the command or setting default_master_connection to the connection you want to work with
* The channel name supports up to 64 bytes, and is not case sensitive
* The connection name and for channel syntax cannot be used at the same time, otherwise an error will be reported
* MariaDB syntax is highly compatible with MySQL, so there is no special SQL_MODE set like Oracle/SQL Server and other databases, FOR CHANNEL is not affected by SQL_MODE

h1. new syntax for MariaDB
h2. CHANGE MASTER
{code:java}
CHANGE MASTER ['connection_name'] TO master_def [, master_def] ... [FOR CHANNEL 'channel_name']
{code}

h2. FLUSH RELAY LOG

{code:java}
FLUSH RELAY LOGS ['connection_name' | FOR CHANNEL 'channel_name']
{code}

h2. RESET SLAVE

{code:java}
RESET SLAVE ['connection_name'] [ALL] [FOR CHANNEL 'channel_name']
{code}

h2. SHOW RELAY LOG EVENT

{code:java}
SHOW RELAYLOG ['connection_name'] EVENTS [IN 'log_name'] [FROM pos] [LIMIT [offset,] row_count] [ FOR CHANNEL 'channel_name']
{code}

h2. SHOW SLAVE STATUS

{code:java}
SHOW SLAVE ['connection_name'] STATUS [FOR CHANNEL 'channel_name']
{code}

h2. START SLAVE

{code:java}
START SLAVE ['connection_name'] [thread_type [, thread_type] ... ] [FOR CHANNEL 'channel_name']
{code}

h2. STOP SLAVE

{code:java}
STOP SLAVE ['connection_name'] [thread_type [, thread_type] ... ] [FOR CHANNEL 'channel_name']
{code}

woqutech.com made changes - 2021-08-16 01:33

Comment

[

- Without changing the original implementation of MariaDB, it is compatible with MySQL syntax, so we can only modify yacc and lex
- Define CHANNEL related tokens in yacc and lex
  - sql_yacc.yy
      %token <kwd> CHANNEL_SYM
  - lex.h
      { "CHANNEL", SYM(CHANNEL_SYM)},

- Modify the detection of the rule part, and the corresponding results, so that MariaDB performs the same operation after detecting [FOR CHANNEL'channel_name'] and after detecting ['connection_name'].
  - define [FOR CHANNEL'channel_name']
      optional_for_channel:
              /* empty */
                {
                  /*do nothing */
                }
              | for_channel

              ;

      for_channel:
              FOR_SYM CHANNEL_SYM TEXT_STRING_sys
              {
                if (Lex->mi.connection_name.str != NULL)
                {
                  my_yyabort_error((ER_WRONG_ARGUMENTS, MYF(0), "CONNECTION_NAME AND FOR CHANNEL CAN NOT BE SPECIFIED AT THE SAME TIME)"));
                }
                else
                {
                  Lex->mi.connection_name= $3;
      #ifdef HAVE_REPLICATION
                 if (unlikely(check_master_connection_name(&$3)))
                    my_yyabort_error((ER_WRONG_ARGUMENTS, MYF(0), "MASTER_CONNECTION_NAME"));
      #endif
                }

               }
               ;

  - CHANGE MASTER
  CHANGE MASTER ['connection_name'] TO master_def [, master_def] ... [FOR CHANNEL 'channel_name']
      change:
                CHANGE MASTER_SYM optional_connection_name TO_SYM
                {
                  Lex->sql_command = SQLCOM_CHANGE_MASTER;
                }
                master_defs
                { }
                optional_for_channel
                { }
              ;

  - FLUSH RELAY LOGS
  FLUSH RELAY LOGS ['connection_name' | FOR CHANNEL 'channel_name']
      | RELAY LOGS_SYM optional_connection_name optional_for_channel
      {
          LEX *lex= Lex;
          if (unlikely(lex->type & REFRESH_RELAY_LOG))
            my_yyabort_error((ER_WRONG_USAGE, MYF(0), "FLUSH", "RELAY LOGS"));
          lex->type|= REFRESH_RELAY_LOG;
          lex->relay_log_connection_name= lex->mi.connection_name;
      }

  - RESET SLAVE
  RESET SLAVE ['connection_name'] [ALL] [FOR CHANNEL 'channel_name']
      reset_option:
                SLAVE { Lex->type|= REFRESH_SLAVE; }
                optional_connection_name
                slave_reset_options optional_for_channel
                { }

  - SHOW RELAYLOG
  SHOW RELAYLOG ['connection_name'] EVENTS [IN 'log_name'] [FROM pos] [LIMIT [offset,] row_count] [ FOR CHANNEL 'channel_name']
      | RELAYLOG_SYM optional_connection_name EVENTS_SYM binlog_in binlog_from
      {
          LEX *lex= Lex;
          lex->sql_command= SQLCOM_SHOW_RELAYLOG_EVENTS;
      }
      opt_global_limit_clause optional_for_channel
      { }

  - SHOW SLAVE STATUS
  SHOW SLAVE ['connection_name'] STATUS [FOR CHANNEL 'channel_name']
       | SLAVE optional_connection_name STATUS_SYM optional_for_channel
       {
          if (!(Lex->m_sql_cmd= new (thd->mem_root)
            Sql_cmd_show_slave_status()))
          MYSQL_YYABORT;
          Lex->sql_command = SQLCOM_SHOW_SLAVE_STAT;
       }

  - START SLAVE
  START SLAVE ['connection_name'] [thread_type [, thread_type] ... ] [FOR CHANNEL 'channel_name']
      START_SYM SLAVE optional_connection_name slave_thread_opts optional_for_channel
      {
          LEX *lex=Lex;
          lex->sql_command = SQLCOM_SLAVE_START;
          lex->type = 0;
          /* If you change this code don't forget to update SLAVE START too */
      }
      slave_until
      {}

  - STOP SLAVE
  STOP SLAVE ['connection_name'] [thread_type [, thread_type] ... ] [FOR CHANNEL 'channel_name']
      | STOP_SYM SLAVE optional_connection_name slave_thread_opts optional_for_channel
      {
          LEX *lex=Lex;
          lex->sql_command = SQLCOM_SLAVE_STOP;
          lex->type = 0;
          /* If you change this code don't forget to update SLAVE STOP too */
      }


]

woqutech.com made changes - 2021-08-18 09:16

Attachment

for_channel.patch [ 58582 ]

woqutech.com made changes - 2021-08-20 06:06

Description

_emphasized text_h1. backugroud
MariaDB and MySQL both implement the multi-source replication, but their usage and internal implementation are different. In order to facilitate the migration of MySQL users to MariaDB, we want to support MySQL syntax

h1. describe
* For CHANGE MASTER/FLUSH RELAY LOG/RESET SLAVE/SHOW RELAY LOG EVENT/SHOW SLAVE STATUS/START SLAVE/STOP SLAVE commands support FOR CHANNEL syntax
* "FOR CHANNEL" is just an alias for connection\_name, does not change the original implementation, all behaviors are consistent with MariaDB, so some operations are not compatible with MySQL, For example:
(MySQL) When a replica has multiple channels and a FOR CHANNEL channel option is not specified, a valid statement generally acts on all available channels, with some specific exceptions.
(MariaDB) You specify which primary connection you want to work with by either specifying the connection name in the command or setting default_master_connection to the connection you want to work with
* The channel name supports up to 64 bytes, and is not case sensitive
* The connection name and for channel syntax cannot be used at the same time, otherwise an error will be reported
* MariaDB syntax is highly compatible with MySQL, so there is no special SQL_MODE set like Oracle/SQL Server and other databases, FOR CHANNEL is not affected by SQL_MODE

h1. new syntax for MariaDB
h2. CHANGE MASTER
{code:java}
CHANGE MASTER ['connection_name'] TO master_def [, master_def] ... [FOR CHANNEL 'channel_name']
{code}

h2. FLUSH RELAY LOG

{code:java}
FLUSH RELAY LOGS ['connection_name' | FOR CHANNEL 'channel_name']
{code}

h2. RESET SLAVE

{code:java}
RESET SLAVE ['connection_name'] [ALL] [FOR CHANNEL 'channel_name']
{code}

h2. SHOW RELAY LOG EVENT

{code:java}
SHOW RELAYLOG ['connection_name'] EVENTS [IN 'log_name'] [FROM pos] [LIMIT [offset,] row_count] [ FOR CHANNEL 'channel_name']
{code}

h2. SHOW SLAVE STATUS

{code:java}
SHOW SLAVE ['connection_name'] STATUS [FOR CHANNEL 'channel_name']
{code}

h2. START SLAVE

{code:java}
START SLAVE ['connection_name'] [thread_type [, thread_type] ... ] [FOR CHANNEL 'channel_name']
{code}

h2. STOP SLAVE

{code:java}
STOP SLAVE ['connection_name'] [thread_type [, thread_type] ... ] [FOR CHANNEL 'channel_name']
{code}

_emphasized text_h1. backugroud
MariaDB and MySQL both implement the multi-source replication, but their usage and internal implementation are different. In order to facilitate the migration of MySQL users to MariaDB, we want to support MySQL syntax

h1. describe
* For CHANGE MASTER/FLUSH RELAY LOG/RESET SLAVE/SHOW RELAY LOG EVENT/SHOW SLAVE STATUS/START SLAVE/STOP SLAVE commands support FOR CHANNEL syntax
* "FOR CHANNEL" is just an alias for connection\_name, does not change the original implementation, all behaviors are consistent with MariaDB, so some operations are not compatible with MySQL, For example:
(MySQL) When a replica has multiple channels and a FOR CHANNEL channel option is not specified, a valid statement generally acts on all available channels, with some specific exceptions.
(MariaDB) You specify which primary connection you want to work with by either specifying the connection name in the command or setting default_master_connection to the connection you want to work with
* The channel name supports up to 64 bytes, and is not case sensitive
* The connection name and for channel syntax cannot be used at the same time, otherwise an error will be reported
* MariaDB syntax is highly compatible with MySQL, so there is no special SQL_MODE set like Oracle/SQL Server and other databases, FOR CHANNEL is not affected by SQL_MODE

h1. new syntax for MariaDB
h2. CHANGE MASTER
{code:java}
CHANGE MASTER ['connection_name'] TO master_def [, master_def] ... [FOR CHANNEL 'connection_name']
{code}

h2. FLUSH RELAY LOG

{code:java}
FLUSH RELAY LOGS ['connection_name' | FOR CHANNEL 'connection_name']
{code}

h2. RESET SLAVE

{code:java}
RESET SLAVE ['connection_name'] [ALL] [FOR CHANNEL 'connection_name']
{code}

h2. SHOW RELAY LOG EVENT

{code:java}
SHOW RELAYLOG ['connection_name'] EVENTS [IN 'log_name'] [FROM pos] [LIMIT [offset,] row_count] [ FOR CHANNEL 'connection_name']
{code}

h2. SHOW SLAVE STATUS

{code:java}
SHOW SLAVE ['connection_name'] STATUS [FOR CHANNEL 'connection_name']
{code}

h2. START SLAVE

{code:java}
START SLAVE ['connection_name'] [thread_type [, thread_type] ... ] [FOR CHANNEL 'connection_name']
{code}

h2. STOP SLAVE

{code:java}
STOP SLAVE ['connection_name'] [thread_type [, thread_type] ... ] [FOR CHANNEL 'connection_name']
{code}

woqutech.com made changes - 2021-08-20 06:06

Description

_emphasized text_h1. backugroud
MariaDB and MySQL both implement the multi-source replication, but their usage and internal implementation are different. In order to facilitate the migration of MySQL users to MariaDB, we want to support MySQL syntax

h1. describe
* For CHANGE MASTER/FLUSH RELAY LOG/RESET SLAVE/SHOW RELAY LOG EVENT/SHOW SLAVE STATUS/START SLAVE/STOP SLAVE commands support FOR CHANNEL syntax
* "FOR CHANNEL" is just an alias for connection\_name, does not change the original implementation, all behaviors are consistent with MariaDB, so some operations are not compatible with MySQL, For example:
(MySQL) When a replica has multiple channels and a FOR CHANNEL channel option is not specified, a valid statement generally acts on all available channels, with some specific exceptions.
(MariaDB) You specify which primary connection you want to work with by either specifying the connection name in the command or setting default_master_connection to the connection you want to work with
* The channel name supports up to 64 bytes, and is not case sensitive
* The connection name and for channel syntax cannot be used at the same time, otherwise an error will be reported
* MariaDB syntax is highly compatible with MySQL, so there is no special SQL_MODE set like Oracle/SQL Server and other databases, FOR CHANNEL is not affected by SQL_MODE

h1. new syntax for MariaDB
h2. CHANGE MASTER
{code:java}
CHANGE MASTER ['connection_name'] TO master_def [, master_def] ... [FOR CHANNEL 'connection_name']
{code}

h2. FLUSH RELAY LOG

{code:java}
FLUSH RELAY LOGS ['connection_name' | FOR CHANNEL 'connection_name']
{code}

h2. RESET SLAVE

{code:java}
RESET SLAVE ['connection_name'] [ALL] [FOR CHANNEL 'connection_name']
{code}

h2. SHOW RELAY LOG EVENT

{code:java}
SHOW RELAYLOG ['connection_name'] EVENTS [IN 'log_name'] [FROM pos] [LIMIT [offset,] row_count] [ FOR CHANNEL 'connection_name']
{code}

h2. SHOW SLAVE STATUS

{code:java}
SHOW SLAVE ['connection_name'] STATUS [FOR CHANNEL 'connection_name']
{code}

h2. START SLAVE

{code:java}
START SLAVE ['connection_name'] [thread_type [, thread_type] ... ] [FOR CHANNEL 'connection_name']
{code}

h2. STOP SLAVE

{code:java}
STOP SLAVE ['connection_name'] [thread_type [, thread_type] ... ] [FOR CHANNEL 'connection_name']
{code}

MariaDB and MySQL both implement the multi-source replication, but their usage and internal implementation are different. In order to facilitate the migration of MySQL users to MariaDB, we want to support MySQL syntax

h1. describe
* For CHANGE MASTER/FLUSH RELAY LOG/RESET SLAVE/SHOW RELAY LOG EVENT/SHOW SLAVE STATUS/START SLAVE/STOP SLAVE commands support FOR CHANNEL syntax
* "FOR CHANNEL" is just an alias for connection\_name, does not change the original implementation, all behaviors are consistent with MariaDB, so some operations are not compatible with MySQL, For example:
(MySQL) When a replica has multiple channels and a FOR CHANNEL channel option is not specified, a valid statement generally acts on all available channels, with some specific exceptions.
(MariaDB) You specify which primary connection you want to work with by either specifying the connection name in the command or setting default_master_connection to the connection you want to work with
* The channel name supports up to 64 bytes, and is not case sensitive
* The connection name and for channel syntax cannot be used at the same time, otherwise an error will be reported
* MariaDB syntax is highly compatible with MySQL, so there is no special SQL_MODE set like Oracle/SQL Server and other databases, FOR CHANNEL is not affected by SQL_MODE

h1. new syntax for MariaDB
h2. CHANGE MASTER
{code:java}
CHANGE MASTER ['connection_name'] TO master_def [, master_def] ... [FOR CHANNEL 'connection_name']
{code}

h2. FLUSH RELAY LOG

{code:java}
FLUSH RELAY LOGS ['connection_name' | FOR CHANNEL 'connection_name']
{code}

h2. RESET SLAVE

{code:java}
RESET SLAVE ['connection_name'] [ALL] [FOR CHANNEL 'connection_name']
{code}

h2. SHOW RELAY LOG EVENT

{code:java}
SHOW RELAYLOG ['connection_name'] EVENTS [IN 'log_name'] [FROM pos] [LIMIT [offset,] row_count] [ FOR CHANNEL 'connection_name']
{code}

h2. SHOW SLAVE STATUS

{code:java}
SHOW SLAVE ['connection_name'] STATUS [FOR CHANNEL 'connection_name']
{code}

h2. START SLAVE

{code:java}
START SLAVE ['connection_name'] [thread_type [, thread_type] ... ] [FOR CHANNEL 'connection_name']
{code}

h2. STOP SLAVE

{code:java}
STOP SLAVE ['connection_name'] [thread_type [, thread_type] ... ] [FOR CHANNEL 'connection_name']
{code}

woqutech.com made changes - 2021-08-20 11:31

Comment

[ A comment with security level 'Users' was removed. ]

Michael Widenius made changes - 2021-08-23 21:51

Assignee

Michael Widenius [ monty ]

Michael Widenius made changes - 2021-08-23 21:52

Fix Version/s

10.7.0 [ 26072 ]

Michael Widenius made changes - 2021-08-23 21:52

Status

Open [ 1 ]

In Progress [ 3 ]

Sergei Golubchik made changes - 2021-08-30 10:11

Fix Version/s		10.7 [ 24805 ]
Fix Version/s	10.7.0 [ 26072 ]

Elena Stepanova made changes - 2021-09-02 22:02

Link

This issue relates to TODO-3118 [ TODO-3118 ]

woqutech.com made changes - 2021-09-04 11:45

Attachment

for_chanel_210904.diff [ 58848 ]

Sergei Golubchik made changes - 2021-09-04 12:21

Priority

Major [ 3 ]

Critical [ 2 ]

Sergei Golubchik made changes - 2021-09-06 12:08

Link

This issue relates to TODO-3118 [ TODO-3118 ]

Sergei Golubchik made changes - 2021-09-07 14:11

Assignee

Michael Widenius [ monty ]

Sergei Golubchik [ serg ]

Sergei Golubchik made changes - 2021-09-07 14:11

Status

In Progress [ 3 ]

Stalled [ 10000 ]

Sergei Golubchik made changes - 2021-09-07 14:11

Assignee

Sergei Golubchik [ serg ]

Alice Sherepa [ alice ]

Sergei Golubchik made changes - 2021-09-07 14:12

Link

This issue relates to TODO-3118 [ TODO-3118 ]

Sergei Golubchik made changes - 2021-09-14 18:51

Fix Version/s		10.7.0 [ 26072 ]
Fix Version/s	10.7 [ 24805 ]
Resolution		Fixed [ 1 ]
Status	Stalled [ 10000 ]	Closed [ 6 ]

Sergei Golubchik made changes - 2021-09-14 18:52

Assignee

Alice Sherepa [ alice ]

Michael Widenius [ monty ]

woqutech.com made changes - 2021-09-15 02:01

Attachment

for_channel_test_210915.diff [ 58988 ]

Sergei Golubchik made changes - 2021-12-06 21:24

Workflow

MariaDB v3 [ 124110 ]

MariaDB v4 [ 134460 ]

Angelique Sklavounos (Inactive) made changes - 2022-12-07 21:53

Link

This issue relates to MDEV-23912 [ MDEV-23912 ]

Ralf Gebhardt made changes - 2023-03-21 11:01

Fix Version/s		10.7.1 [ 26120 ]
Fix Version/s	10.7.0 [ 26072 ]

MariaDB Server

multi-source-replication support mysql syntax(for channel)

Details

Description

describe

new syntax for MariaDB

CHANGE MASTER

FLUSH RELAY LOG

RESET SLAVE

SHOW RELAY LOG EVENT

SHOW SLAVE STATUS

START SLAVE

STOP SLAVE

Attachments

Attachments

Issue Links

Activity

People

Dates

Git Integration