This is an automated email from the ASF dual-hosted git repository.

zhangduo pushed a change to branch HBASE-27109/table_based_rqs
in repository https://gitbox.apache.org/repos/asf/hbase.git


 discard 6dd64f1218c HBASE-27213 Add support for claim queue operation (#4708)
 discard 7605530b4a4 HBASE-27212 Implement a new table based replication queue 
storage and make the minimum replication system work (#4672)
     add f238a92b6df HBASE-27129 Add a config that allows us to configure 
region-level storage policies (#4547)
     new 37f92c068cc HBASE-27212 Implement a new table based replication queue 
storage and make the minimum replication system work (#4672)
     new ad9d11753cd HBASE-27213 Add support for claim queue operation (#4708)

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   (6dd64f1218c)
            \
             N -- N -- N   refs/heads/HBASE-27109/table_based_rqs (ad9d11753cd)

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 2 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:
 .../java/org/apache/hadoop/hbase/regionserver/HRegion.java |  6 ++++++
 .../hadoop/hbase/regionserver/HRegionFileSystem.java       | 14 ++++++++++++++
 2 files changed, 20 insertions(+)

Reply via email to