. . . . . . . . . . . . . . . . . . . . . . . . . 328 vtexplain -shards 8 -vschema-file vschema.json -schema-file schema.sql -replication-mode “ROW” -output-mode text -sql “SELECT * from users” . . use a region_json vindex to compute the keyspace_id for a customer row using the (id, country) fields. Here’s what the vindex definition looks like: "region_vdx": { "type": "region_json", "params": { { "region_map": "/vt/examples/region_sharding/countries.json", "region_bytes": "1" } }, And we use it thus: "customer": { "column_vindexes": [ { "columns": ["id", "country"], "name": "region_vdx"

. . . . . . . . . . . . . . . . . . . . . . . . . 391 vtexplain -shards 8 -vschema-file vschema.json -schema-file schema.sql -replication-mode “ROW” -output-mode text -sql “SELECT * from users” . . NotSupported transaction_write_set_extraction NotSupported default_week_format ReservedConn end_markers_in_json ReservedConn eq_range_index_dive_limit ReservedConn explicit_defaults_for_timestamp ReservedConn foreign_key_checks standard way to do this conversion. It would be nice if protos supported this na- tively as they do for json. We do have the option of using this code to build our own yaml to proto converter: https://github

NotSupported transaction_write_set_extraction NotSupported default_week_format ReservedConn end_markers_in_json ReservedConn eq_range_index_dive_limit ReservedConn 24 System variable Handled explicit_defaults_for_timestamp standard way to do this conversion. It would be nice if protos supported this na- tively as they do for json. We do have the option of using this code to build our own yaml to proto converter: https://github Protobuf We explored the use of protobufs for converting to and from yaml. However, the protobuf JSON implementation, which was required to correctly parse enums, was unable to preserve the original values

. . . . . . . . . . . . . . . . . . . . . . . . . 428 vtexplain -shards 8 -vschema-file vschema.json -schema-file schema.sql -replication-mode “ROW” -output-mode text -sql “SELECT * from users” . . NotSupported transaction_write_set_extraction NotSupported default_week_format ReservedConn end_markers_in_json ReservedConn eq_range_index_dive_limit ReservedConn explicit_defaults_for_timestamp ReservedConn foreign_key_checks standard way to do this conversion. It would be nice if protos supported this na- tively as they do for json. We do have the option of using this code to build our own yaml to proto converter: https://github

file "./mysql_auth_server_static_creds.json" \ In this example, vtgate accepts MySQL connections on port 15306 and the authentication info is stored in the json file. So, you should be able to connect create_commerce_schema.sql)" commerce vtctlclient ApplyVSchema -vschema="$(cat vschema_commerce_initial.json)" commerce Connect to your cluster You should now be able to connect to the VTGate Server in your [-cells=c1,c2,...] [-skip_rebuild] [-dry-run] Syntax Resharding Routing rules can be specified using JSON format. Here’s an example: {"rules": [ { "from_table": "t@rdonly", "to_tables": ["target.t"] }

. . . . . . . . . . . . . . . . . 507 vtexplain -vschema-file vschema.json -schema-file schema.sql -ks-shard-map shardmaps.json -replication-mode “ROW” -output-mode text -sql “SELECT FROM users; SELECT NotSupported transaction_write_set_extraction NotSupported default_week_format ReservedConn end_markers_in_json ReservedConn eq_range_index_dive_limit ReservedConn explicit_defaults_for_timestamp ReservedConn foreign_key_checks standard way to do this conversion. It would be nice if protos supported this natively as they do for json. We do have the option of using this code to build our own yaml to proto converter: https://github

file "./mysql_auth_server_static_creds.json" \ In this example, vtgate accepts MySQL connections on port 15306 and the authentication info is stored in the json file. So, you should be able to connect [-cells=c1,c2,...] [-skip_rebuild] [-dry-run] Syntax Resharding Routing rules can be specified using JSON format. Here’s an example: {"rules": [ { "from_table": "t@rdonly", "to_tables": ["target.t"] } t", "to_tables": ["source.t"] }, { "from_table": "t", "to_tables": ["source.t"] } ]} The above JSON specifies the following rules: * If you sent a query accessing t for an rdonly instance, then it would

file "./mysql_auth_server_static_creds.json" \ In this example, vtgate accepts MySQL connections on port 15306 and the authentication info is stored in the json file. So, you should be able to connect [-cells=c1,c2,...] [-skip_rebuild] [-dry-run] Syntax Resharding Routing rules can be specified using JSON format. Here’s an example: {"rules": [ { "from_table": "t@rdonly", "to_tables": ["target.t"] } "to_tables": ["source.t"] }, { "from_table": "t", "to_tables": ["source.t"] } ]} 57 The above JSON specifies the following rules: * If you sent a query accessing t for an rdonly instance, then it would

sent 100,000 requests. import requests import json url = 'http://localhost:14200/api/vtctlds' j = 0 for i in range(100000): x = requests.get(url) resp = json.loads(x.text) if resp["result"]["vtctlds"][0]["hostname"]