740e937210
proto files layout: protobuf/client - client to server messages, client rpc service and protos, used in hbase-client exclusively; protobuf/rest - hbase-rest messages; protobuf/rpc - rpc and post-rpc tracing messages; protobuf/server/coprocessor - coprocessor rpc services; protobuf/server/coprocessor/example - coprocessors rpc services examples from hbase-examples; protobuf/server/io - filesystem and hbase-server/io protos; protobuf/server/maser - master rpc services and messages; protobuf/server/region - region rpc services and messages (except client rpc service, which is in Client.proto); protobuf/server/rsgroup - rsgroup protos; protobuf/server/zookeeper - protos for zookeeper and ones used exclusively in hbase-zookeeper module; protobuf/server - protos used across other server protos; protobuf/test - protos used in tests; protobuf/ - protos used across other protos, exclusive for hbase-mapreduce and hbase-backup, other protos. Signed-off-by: Jan Hentschel <jan.hentschel@ultratendency.com> Signed-off-by: Duo Zhang <zhangduo@apache.org> |
||
|---|---|---|
| .. | ||
| src | ||
| README.txt | ||
| pom.xml | ||
README.txt
ON PROTOBUFS
This maven module has protobuf definition files ('.protos') used by hbase
Coprocessor Endpoints that ship with hbase core (including tests). Coprocessor
Endpoints are meant to be standalone, independent code not reliant on hbase
internals. They define their Service using protobuf. The protobuf version
they use can be distinct from that used by HBase internally since HBase started
shading its protobuf references. Endpoints have no access to the shaded protobuf
hbase uses. They do have access to the content of hbase-protocol -- the
.protos found in this module -- but avoid using as much of this as you can as it is
liable to change.
Generation of java files from protobuf .proto files included here is done as
part of the build.