0611ca49ec
HBASE-25267 Make SSL keystore type configurable in HBase RESTServer In this patch I want to introduce the hbase.rest.ssl.keystore.type parameter, enabling us to customize the keystore type for the REST server. If the parameter is not provided, then we should fall-back to the current behaviour (which assumes keystore type JKS). This is similar to how we already configure the InfoServer objects with the ssl.server.keystore.type parameter to set up HTTPS for the various admin UIs. Signed-off-by: Wellington Chevreuil <wellington.chevreuil@gmail.com> Signed-off-by: Balazs Meszaros <meszibalu@apache.org> Signed-off-by: Sean Busbey <busbey@apache.org> |
||
|---|---|---|
| .. | ||
| src | ||
| README.txt | ||
| pom.xml | ||
README.txt
ON PROTOBUFS
This maven module has core protobuf definition files ('.protos') used by hbase
REST that ship with hbase core including tests. The protobuf version
they use can be distinct from that used by HBase internally since HBase started
shading its protobuf references. REST Endpoints have no access to the shaded protobuf
hbase uses. They do have access to the content of hbase-protocol -- the
.protos found in here -- 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.