. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 System variable types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . them using SET: SET @my_user_variable = 'foobar' And later there can be queries using for example SELECT: > SELECT @my_user_variable; +-------------------+ | @my_user_variable | +-------------------+ | rewrite the query before sending it down. If we were to write something like: WHERE col = @my_user_variable What MySQL will see is: WHERE col = 'foobar' This way, no session state is needed to evaluate

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 System variable types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . them using SET: SET @my_user_variable = 'foobar' And later there can be queries using for example SELECT: > SELECT @my_user_variable; +-------------------+ | @my_user_variable | +-------------------+ | rewrite the query before sending it down. If we were to write something like: WHERE col = @my_user_variable What MySQL will see is: WHERE col = 'foobar' This way, no session state is needed to evaluate

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 System variable types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . them using SET: SET @my_user_variable = 'foobar' And later there can be queries using for example SELECT: > SELECT @my_user_variable; +-------------------+ | @my_user_variable | +-------------------+ | rewrite the query before sending it down. If we were to write something like: WHERE col = @my_user_variable What MySQL will see is: WHERE col = 'foobar' This way, no session state is needed to evaluate

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 System variable types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . them using SET: SET @my_user_variable = 'foobar' And later there can be queries using for example SELECT: > SELECT @my_user_variable; +-------------------+ | @my_user_variable | +-------------------+ | rewrite the query before sending it down. If we were to write something like: WHERE col = @my_user_variable What MySQL will see is: WHERE col = 'foobar' This way, no session state is needed to evaluate

them using SET: SET @my_user_variable = 'foobar' And later there can be queries using for example SELECT: > SELECT @my_user_variable; +-------------------+ | @my_user_variable | +-------------------+ | rewrite the query before sending it down. If we were to write something like: WHERE col = @my_user_variable What MySQL will see is: WHERE col = 'foobar' This way, no session state is needed to evaluate These are settings that should not change, but Vitess will allow SET statements that try to set the variable to whatever it already is. • Not supported. For these settings, attempting to change them will

sudo mv * /usr/local/vitess/ 34 Make sure to add /usr/local/vitess/bin to the PATH environment variable. You can do this by adding the following to your $HOME/.bashrc file: export PATH=/usr/local/vitess/bin:${PATH} the directory /vitess/cell1: # Reference cell1 in the global topology service: # (the TOPOLOGY variable is defined in the previous section) vtctl $TOPOLOGY AddCellInfo \ -server_address http://cell1_server1 under the directory vitess/cell1: # Reference cell1 in the global topology service: # (the TOPOLOGY variable is defined in the previous section) vtctl $TOPOLOGY AddCellInfo \ -server_address cell1_server1:cell1_port

For subsequent commands, it will be convenient to capture the name of the release and save into a variable: export release=$(helm ls -q) For a vertical split, we first need to create a special served_from /usr/local/vitess sudo mv * /usr/local/vitess/ Make sure to add /usr/local/vitess/bin to the PATH environment variable. You can do this by adding the following to your $HOME/.bashrc file: export PATH=/usr/local/vitess/bin:${PATH} directory /vitess/cell1: 64 # Reference cell1 in the global topology service: # (the TOPOLOGY variable is defined in the previous section) vtctl $TOPOLOGY AddCellInfo \ -server_address http://cell1_server1

/usr/local/vitess sudo mv * /usr/local/vitess/ Make sure to add /usr/local/vitess/bin to the PATH environment variable. You can do this by adding the following to your $HOME/.bashrc file: export PATH=/usr/local/vitess/bin:${PATH} the directory /vitess/cell1: # Reference cell1 in the global topology service: # (the TOPOLOGY variable is defined in the previous section) vtctl $TOPOLOGY AddCellInfo \ -server_address http://cell1_server1 under the directory vitess/cell1: # Reference cell1 in the global topology service: # (the TOPOLOGY variable is defined in the previous section) vtctl $TOPOLOGY AddCellInfo \ -server_address cell1_server1:cell1_port

but it is also possible to write them as hexadecimal strings prefixed by 0x. As the variable deduplication ignores strings with the 0x prefix, those values are not redacted. This behavior