records, and the local SrvKeyspace records. Exploring the data in a Topology Service We store the proto3 serialized binary data for each object. We use the following paths for the data, in all implementations: -decode_proto option: TOPOLOGY="-topo_implementation zk2 -topo_global_server_address global_server1 ,global_server2 -topo_global_root /vitess/global" $ vtctl $TOPOLOGY TopoCat -decode_proto -long / contains a topology browser (use the Topology tab on the left side). It will display the various proto files, decoded. Implementations The Topology Service interfaces are defined in our code in go/vt/topo/

records, and the local SrvKeyspace records. Exploring the data in a Topology Service We store the proto3 serialized binary data for each object. We use the following paths for the data, in all implementations: -decode_proto option: 55 TOPOLOGY="-topo_implementation zk2 -topo_global_server_address global_server1 ,global_server2 -topo_global_root /vitess/global" $ vtctl $TOPOLOGY TopoCat -decode_proto -long contains a topology browser (use the Topology tab on the left side). It will display the various proto files, decoded. Implementations The Topology Service interfaces are defined in our code in go/vt/topo/

records, and the local SrvKeyspace records. 62 Exploring the data in a Topology Service We store the proto3 serialized binary data for each object. We use the following paths for the data, in all implementations: -decode_proto option: TOPOLOGY="-topo_implementation zk2 -topo_global_server_address global_server1 ,global_server2 -topo_global_root /vitess/global" $ vtctl $TOPOLOGY TopoCat -decode_proto -long / contains a topology browser (use the Topology tab on the left side). It will display the various proto files, decoded. Implementations The Topology Service interfaces are defined in our code in go/vt/topo/

records, and the local SrvKeyspace records. Exploring the data in a Topology Service We store the proto3 serialized binary data for each object. We use the following paths for the data, in all implementations: -decode_proto option: TOPOLOGY="-topo_implementation zk2 -topo_global_server_address global_server1 ,global_server2 -topo_global_root /vitess/global" $ vtctl $TOPOLOGY TopoCat -decode_proto -long / contains a topology browser (use the Topology tab on the left side). It will display the various proto files, decoded. 77 Implementations The Topology Service interfaces are defined in our code in go/vt/topo/

all formats to yaml. If this sounds viable, we can convert the Config struct to be generated from a proto, and then have yaml tags that can convert into it. This will future-proof us in case we decide to 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.com/golang/protobuf/blob/master/jsonpb/jsonpb.go. TabletManager The TabletManager records, and the local SrvKeyspace records. Exploring the data in a Topology Service We store the proto3 serialized binary data for each object. We use the following paths for the data, in all implementations:

skew detection and alignment feature in a VStream client: import vtgatepb "vitess.io/vitess/go/vt/proto/vtgate" ... ... flags := &vtgatepb.VStreamFlags{}; flags.MinimizeSkew = true; reader , err := conn all formats to yaml. If this sounds viable, we can convert the Config struct to be generated from a proto, and then have yaml tags that can convert into it. This will future-proof us in case we decide to 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.com/golang/protobuf/blob/master/jsonpb/jsonpb.go. TabletManager The TabletManager

detection and alignment feature in a VStream client: 53 import vtgatepb "vitess.io/vitess/go/vt/proto/vtgate" ... ... flags := &vtgatepb.VStreamFlags{}; flags.MinimizeSkew = true; reader , err := conn all formats to yaml. If this sounds viable, we can convert the Config struct to be generated from a proto, and then have yaml tags that can convert into it. This will future-proof us in case we decide to 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.com/golang/protobuf/blob/master/jsonpb/jsonpb.go. TabletManager The TabletManager

detection and alignment feature in a VStream client: 78 import vtgatepb "vitess.io/vitess/go/vt/proto/vtgate" ... ... flags := &vtgatepb.VStreamFlags{}; flags.MinimizeSkew = true; reader , err := conn all formats to yaml. If this sounds viable, we can convert the Config struct to be generated from a proto, and then have yaml tags that can convert into it. This will future-proof us in case we decide to 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.com/golang/ protobuf/blob/master/jsonpb/encode.go. TabletManager The TabletManager