зеркало из https://github.com/github/vitess-gh.git
b48a84ca64
The vtgate API takes a starting timestamp, or a starting EventToken. It will only use the starting EventToken if it's relevant. This is mostly for tests, but could be used by real clients too to avoid the timestamp search on the servers. The only restriction in the vtgate routing implementation is that a query can only end up on one shard. The stream aggregation code inside vtgate will be added later. This change includes: - proto changes. - implementing the server side interface. - implementing the client side interface. - adding a vtctl VtTabletUpdateStream command to stream from a given tablet. This is used in end-to-end tests. - using the python vtgate_client update_stream API in all end-to-end tests. - removing the python vttablet direct stream_update API. - vtgate now better preserves remote errors through its API now, as withSuffix and withPrefix will preserve the error codes of all VtError, not just *VitessError. - Also adding callerid vtgateclienttest tests for all API calls. |
||
|---|---|---|
| .. | ||
| automation.proto | ||
| automationservice.proto | ||
| binlogdata.proto | ||
| binlogservice.proto | ||
| logutil.proto | ||
| mysqlctl.proto | ||
| query.proto | ||
| queryservice.proto | ||
| replicationdata.proto | ||
| tableacl.proto | ||
| tabletmanagerdata.proto | ||
| tabletmanagerservice.proto | ||
| throttlerdata.proto | ||
| throttlerservice.proto | ||
| topodata.proto | ||
| vschema.proto | ||
| vtctldata.proto | ||
| vtctlservice.proto | ||
| vtgate.proto | ||
| vtgateservice.proto | ||
| vtrpc.proto | ||
| vttest.proto | ||
| vtworkerdata.proto | ||
| vtworkerservice.proto | ||
| workflow.proto | ||