vitess-gh

Граф коммитов

Автор	SHA1	Сообщение	Дата
Alain Jobart	63daac2a5d	Now using strings in remote RPC communication for replication position. Much simpler than the big proto file.	2015-07-24 10:29:28 -07:00
Alain Jobart	0a4d922670	Adding a few proto3 methods in preparation for tabletmanager.	2015-06-25 14:54:46 -07:00
Alain Jobart	eac090cd50	Renaming a few proto files. Turns out the proto we use in google3 cannot have the same <package name>.<data type> as these, or we cannot load them at the same time. So to fix this: - renaming the conflicting ones from xxx.proto to xxxdata.proto. - renaming vtgateservice.VTGate to vtgateservice.Vitess Note we can still change the names I chose here, just not back to conflicting ones. If anyone has better ideas, we can implement in subsequent changes. This is to get the import to google3 unstuck.	2015-06-19 08:20:58 -07:00

Автор

SHA1

Сообщение

Дата

Alain Jobart

63daac2a5d

Now using strings in remote RPC communication for replication position.

Much simpler than the big proto file.

2015-07-24 10:29:28 -07:00

Alain Jobart

0a4d922670

Adding a few proto3 methods in preparation for tabletmanager.

2015-06-25 14:54:46 -07:00

Alain Jobart

eac090cd50

Renaming a few proto files. Turns out the proto we use in google3

cannot have the same <package name>.<data type> as these, or we cannot
load them at the same time. So to fix this:
- renaming the conflicting ones from xxx.proto to xxxdata.proto.
- renaming vtgateservice.VTGate to vtgateservice.Vitess

Note we can still change the names I chose here, just not back to
conflicting ones. If anyone has better ideas, we can implement
in subsequent changes. This is to get the import to google3 unstuck.

2015-06-19 08:20:58 -07:00

3 Коммитов