hbase/hbase-endpoint
Josh Elser 8b66dea2ff HBASE-21281 Upgrade bouncycastle to latest
BC 1.47 introduced some incompatible API changes which came in via
a new Maven artifact. We don't use any changed API in HBase. This
also removes some unnecessary dependencies on bcprov in other
modules (presumably, they are vestiges)

Signed-off-by: Mike Drob <mdrob@apache.org>
Signed-off-by: Ted Yu <tedyu@apache.org>
2018-10-11 11:02:32 -04:00
..
src HBASE-20950 Helper method to configure secure DFS cluster for tests 2018-07-31 13:36:17 -07:00
README.txt HBASE-17056 Remove checked in PB generated files 2017-08-02 09:33:20 -07:00
pom.xml HBASE-21281 Upgrade bouncycastle to latest 2018-10-11 11:02:32 -04:00

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.