If you do decide to select to define the mapping for either data or indexes, you may do so. If you define one and not the other, Regatta will complete the definition for you. For example, if you do map the table to some devices but not decaler where an indexed key should go, Regatta will select a random device and map the index to it.

The first command should display the devices that are used in the cluster. We enter SHOW DEVICES in the WebCLI command line:

SHOW DEVICES

The next command will be the CREATE TABLE command. This command will look as follows (note the usage of the devices). Let’s create a similar table called workers. Enter the following command:

CREATE TABLE workers (
 worker_key INT PRIMARY KEY INDEX WITH (devices = (m10d1)),
 worker_name VARCHAR(40) NOT NULL,
 worker_salary INT,
 worker_department VARCHAR(50) NOT NULL)
WITH (devices = (m10d1))

Running it will create the desired table.

Enter the SQL show tables command:

SHOW TABLES

We can see the table with all the columns and the device mapping. Note that in the workers table, the data is only mapped once to the device since this is what we chose as opposed to employees where Regatta mapped it 3 times.

We will continue here using the employees table.