зеркало из https://github.com/github/vitess-gh.git
c1f79617e7
* Fix ordering when error happens during stream setup (#11592) * Fix ordering when error happens during stream setup When we already have an error during the stream setup, that errors needs to be returned immediately. Otherwise the stream will already be started and the error message is never returned to the client and it silently looks like a success even if it's a failure. This in turn can result in an empty result for example when an error would have been expected. Signed-off-by: Dirkjan Bussink <d.bussink@gmail.com> * Add a bunch of testing to verify stream execute behavior Signed-off-by: Dirkjan Bussink <d.bussink@gmail.com> Signed-off-by: Dirkjan Bussink <d.bussink@gmail.com> * Send errors in stream instead of a grpc error from streaming rpcs when transaction or reserved connection is acquired (#11656) * wip Signed-off-by: Harshit Gangal <harshit@planetscale.com> * feat: send errors in stream instead of a grpc error from streaming rpcs Signed-off-by: Manan Gupta <manan@planetscale.com> Signed-off-by: Harshit Gangal <harshit@planetscale.com> Signed-off-by: Manan Gupta <manan@planetscale.com> Co-authored-by: Manan Gupta <manan@planetscale.com> Signed-off-by: Dirkjan Bussink <d.bussink@gmail.com> Signed-off-by: Harshit Gangal <harshit@planetscale.com> Signed-off-by: Manan Gupta <manan@planetscale.com> Co-authored-by: Dirkjan Bussink <d.bussink@gmail.com> Co-authored-by: Manan Gupta <manan@planetscale.com> |
||
---|---|---|
.. | ||
acl | ||
bucketpool | ||
bytes2 | ||
cache | ||
cmd | ||
event | ||
exit | ||
fileutil | ||
flags/endtoend | ||
flagutil | ||
hack | ||
history | ||
internal/flag | ||
ioutil2 | ||
json2 | ||
jsonutil | ||
mathstats | ||
mysql | ||
netutil | ||
pools | ||
protoutil | ||
race | ||
ratelimiter | ||
sqlescape | ||
sqltypes | ||
stats | ||
streamlog | ||
sync2 | ||
tb | ||
test | ||
testfiles | ||
textutil | ||
timer | ||
tools | ||
trace | ||
vt | ||
vtbench | ||
yaml2 | ||
zk/zkctl | ||
README.md |
README.md
This directory contains all the Go code for Vitess.
Most of the packages at the top level are general-purpose and are suitable for use outside Vitess. Packages that are specific to Vitess are in the vt subdirectory. Binaries are in the cmd subdirectory.
Please see GoDoc for a listing of the packages and their purposes.
vt/proto contains the compiled protos for go, one per each directory. When importing these protos (for instance XXX.proto), we rename them on import to XXXpb. For instance:
import (
topodatapb "vitess.io/vitess/go/vt/proto/topodata"
)