Unsharded Keyspace

    << Sharding Guidelines Sharded Keyspace >>

    We are going to start with configuring the product table in the unsharded keyspace product. The schema file should be as follows:

    1. create table product(product_id bigint auto_increment, pname varchar(128), primary key(product_id));

    product_id is the primary key for product, and it is also configured to use MySQL’s auto_increment feature that allows you to automatically generate unique values for it.

    We also need to create a VSchema for the product keyspace and specify that product is a table in the keyspace:

    1. {
    2.   "sharded": false,
    3.   "tables": {
    4.     "product": {}
    5.   }
    6. }

    The json states that the keyspace is not sharded. The product table is specified in the “tables” section of the json. This is because there are other sections that we will introduce later.

    For unsharded keyspaces, no additional metadata is needed for regular tables. So, their entry is empty.

    Alternate VSchema DDL:

    1. alter vschema add table product.product;

    If product is the only keyspace in the cluster, a vschema is unnecessary. Vitess treats single keyspace clusters as a special case and optimistically forwards all queries to that keyspace even if there is no table metadata present in the vschema. But it is a best practice to provide a full vschema to avoid future complications.

    Bringing up the cluster will allow you to access the product table. You can now insert rows into the table:

    1. $ mysql -h 127.0.0.1 -P 12348
    2. [snip]
    3. mysql> insert into product(pname) values ('monitor'), ('keyboard');
    4. Query OK, 2 rows affected (0.00 sec)
    6. mysql> select * from product;
    7. +------------+----------+
    8. | product_id | pname    |
    9. +------------+----------+
    10. |          1 | monitor  |
    11. |          2 | keyboard |
    12. +------------+----------+
    13. 2 rows in set (0.00 sec)

    The insert does not specify values for product_id, because we are relying on MySQL’s auto_increment feature to populate it.

    You will notice that we did not connect to the product database or issue a use statement to select it. This is the ‘unspecified’ mode supported by Vitess. As long as a table name can be uniquely identified from the vschemas, Vitess will automatically direct the query to the correct keyspace.

    You can also connect or specify keyspaces as if they were MySQL databases. The following constructs are valid:

    1. mysql> select * from product.product;
    2. +------------+----------+
    3. | product_id | pname    |
    4. +------------+----------+
    5. |          1 | monitor  |
    6. |          2 | keyboard |
    7. +------------+----------+
    8. 2 rows in set (0.00 sec)
    10. mysql> use product;
    11. Reading table information for completion of table and column names
    12. You can turn off this feature to get a quicker startup with -A
    14. Database changed
    15. mysql> select * from product;
    16. +------------+----------+
    17. | product_id | pname    |
    18. +------------+----------+
    19. |          1 | monitor  |
    20. |          2 | keyboard |
    21. +------------+----------+
    22. 2 rows in set (0.01 sec)

    << Sharding Guidelines Sharded Keyspace >>