This is an automated email from the ASF dual-hosted git repository.
zhangduo pushed a change to branch HBASE-11288.splittable-meta
in repository https://gitbox.apache.org/repos/asf/hbase.git.
omit 84dfce7 HBASE-24390 Remove RegionInfoBuilder.FIRST_META_REGIONINFO
(#1877)
omit c5a6c95 HBASE-24389 Introduce new master rpc methods to locate meta
region through root region (#1774)
omit a1a3e14 HBASE-24388 Store the locations of meta regions in master
local store (#1746)
add 1164531 HBASE-24884 BulkLoadHFilesTool/LoadIncrementalHFiles should
accept -D options from command line parameters (#2260)
new 24f87c1 HBASE-24388 Store the locations of meta regions in master
local store (#1746)
new 4ac1fcc HBASE-24389 Introduce new master rpc methods to locate meta
region through root region (#1774)
new 9cb6635 HBASE-24390 Remove RegionInfoBuilder.FIRST_META_REGIONINFO
(#1877)
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (84dfce7)
\
N -- N -- N refs/heads/HBASE-11288.splittable-meta (9cb6635)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../apache/hadoop/hbase/tool/BulkLoadHFilesTool.java | 17 ++++++++++++-----
1 file changed, 12 insertions(+), 5 deletions(-)
