[
https://issues.apache.org/jira/browse/HBASE-20533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zheng Hu resolved HBASE-20533.
--
Resolution: Fixed
Hadoop Flags: Reviewed
> Fix the flaky TestAssignmentManagerMetrics
>
[
https://issues.apache.org/jira/browse/HBASE-20639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu reopened HBASE-20639:
> Implement permission checking through AccessController instead of
> RSGroupAdminEndpoint
>
Duo Zhang created HBASE-20659:
-
Summary: Implement a reopen table regions procedure
Key: HBASE-20659
URL: https://issues.apache.org/jira/browse/HBASE-20659
Project: HBase
Issue Type: Bug
Ankit Singhal created HBASE-20658:
-
Summary: Release latch early for ModifyTable and TruncateTable
procedure.
Key: HBASE-20658
URL: https://issues.apache.org/jira/browse/HBASE-20658
Project: HBase
Sergey Soldatov created HBASE-20657:
---
Summary: Retrying RPC call for ModifyTableProcedure may stuck
Key: HBASE-20657
URL: https://issues.apache.org/jira/browse/HBASE-20657
Project: HBase
What version you thinking @chia-ping? If 2.1/3.0, should we instead be
working toward HBASE-16473 *Merge WALEdit and WALKey*? Our WALEdit/WALKey
duplicate info and seem way fatter than they need to be. Would be nice to
revisit these data structures... in light of our experience writing and
Any other feedback here folks?
Mike D, you leaning towards the client tarball or just making sure
I've considered it?
(FWIW, I think the client tarball would work fine practically speaking
and don't feel strongly about either approach.)
On Thu, May 24, 2018 at 1:01 AM, Sean Busbey wrote:
> Hi
