Hi team,
Recently, i'm working on codes related to ACLs module, and HBASE-21255 is the
first one.
It will be appreciated if anyone can spare some cycles to give reviews.
Many thanks!
--
Best regards,
R.C
Oh, typo, 'the make_rc.sh can do everything for you'
张铎(Duo Zhang) 于2018年11月9日周五 上午10:09写道：
> I think for the 2.x release the problem is that we are still busy on
> making the code stable, or speak more clearly, to make the procedure v2
> framework stable... And another big problem is lacking
I think for the 2.x release the problem is that we are still busy on making
the code stable, or speak more clearly, to make the procedure v2 framework
stable... And another big problem is lacking of HBCK2 support. These things
are all big issues which prevent people to upgrade to 2.x.
Once these
Zheng Hu created HBASE-21459:
Summary: More benchmark for evaluating the checkKeyValueBytes's
performance
Key: HBASE-21459
URL: https://issues.apache.org/jira/browse/HBASE-21459
Project: HBase
I think it just shifts the RM burden, no? Like instead of watching e.g.
branch-2.2 I instead need to watch branch-2.
On Thu, Nov 8, 2018, 17:28 Josh Elser I think what I'd be concerned about WRT time-based releases is the
> burden on RM to keep the branch in a good state. Perhaps we need to not
This is an important topic. Thanks for bringing it up.
For what it’s worth, I found the “release train” to work pretty well for
patch releases from 1.1. That was only possible because of the stability of
that branch. After the first couple releases, devs were pretty good about
honoring the “bug
I think what I'd be concerned about WRT time-based releases is the
burden on RM to keep the branch in a good state. Perhaps we need to not
push that onto an RM and do better about sharing that load (looking in
the mirror).
However, I do like time-based releases as a means to avoid "hurt
stack created HBASE-21452:
-
Summary: Illegal character in hbase counters group name
Key: HBASE-21452
URL: https://issues.apache.org/jira/browse/HBASE-21452
Project: HBase
Issue Type: Bug
wenbang created HBASE-21455:
---
Summary: Update filesystem-space quota fail if there is a space
quota for non-existing namespace
Key: HBASE-21455
URL: https://issues.apache.org/jira/browse/HBASE-21455
stack created HBASE-21453:
-
Summary: Convert ReadOnlyZKClient to DEBUG instead of INFO
Key: HBASE-21453
URL: https://issues.apache.org/jira/browse/HBASE-21453
Project: HBase
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HBASE-21439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell reopened HBASE-21439:
Although TestStochasticLoadBalancer passes on all branches, including 1.3/1.5/1
with the
Josh Elser created HBASE-21456:
--
Summary: Make WALFactory only used for creating WALProviders
Key: HBASE-21456
URL: https://issues.apache.org/jira/browse/HBASE-21456
Project: HBase
Issue Type:
stack created HBASE-21458:
-
Summary: Error: Could not find or load main class
org.apache.hadoop.hbase.util.GetJavaProperty
Key: HBASE-21458
URL: https://issues.apache.org/jira/browse/HBASE-21458
Project:
stack created HBASE-21454:
-
Summary: Kill zk spew
Key: HBASE-21454
URL: https://issues.apache.org/jira/browse/HBASE-21454
Project: HBase
Issue Type: Bug
Components: logging, Zookeeper
Should be handled in RPC queues first, before mutation op reaches
RingBuffer, I think.
But to answer your question: the only guarantee HBase provide (promises) is
strictly consistent writes and atomicity for
a single row mutation. No, won't break anything. Permutations of mutations
in an execution
Duo Zhang created HBASE-21451:
-
Summary: The way we maintain the lastestPaths in
ReplicationSourceManager is broken when sync replication is used
Key: HBASE-21451
URL:
Ted Yu created HBASE-21457:
--
Summary: BackupUtils#getWALFilesOlderThan refers to wrong
FileSystem
Key: HBASE-21457
URL: https://issues.apache.org/jira/browse/HBASE-21457
Project: HBase
Issue Type:
17 matches
Mail list logo
