ea08907e08
Makes MergeTableRegionsProcedure do more than just two regions at a time. Compatible as MTRP was done considering one day it'd do more than two at a time. Changes hardcoded assumption that merge parent regions are named mergeA and mergeB in a column on the resultant region. Instead can have N columns on the merged region, one for each parent merged. Column qualifiers all being with 'merge'. Most of code below is undoing the assumption that there are two parents on a merge only. |
||
|---|---|---|
| .. | ||
| 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.