[
https://issues.apache.org/jira/browse/HBASE-28359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Beaudreault resolved HBASE-28359.
---
Fix Version/s: 2.6.0
3.0.0-beta-2
Resolution: Fixed
Viraj Jasani created HBASE-28424:
Summary: Set correct Result to RegionActionResult for successful
Put/Delete mutations
Key: HBASE-28424
URL: https://issues.apache.org/jira/browse/HBASE-28424
Bryan Beaudreault created HBASE-28423:
-
Summary: Improvements to backup of bulkloaded files
Key: HBASE-28423
URL: https://issues.apache.org/jira/browse/HBASE-28423
Project: HBase
Issue
We seem to be in agreement in principle, however the devil is in the
details.
The first step should be moving the diagnostic tools out of the test jars.
Are there any tools we don't want to move out ?
Do the diagnostic tools pull in extra dependencies compared to the current
runtime JARs, and if
[
https://issues.apache.org/jira/browse/HBASE-27230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang reopened HBASE-27230:
---
For backporting to other branches.
> RegionServer should be aborted when WAL.sync throws
[
https://issues.apache.org/jira/browse/HBASE-28417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-28417.
---
Fix Version/s: 2.6.0
2.4.18
3.0.0-beta-2
The thread has gone quiet, so then do we have consensus?
Our objective is to remove ZooKeeper from our public interface, remaking it
as an internal concern. Connecting to a cluster via ZooKeeper quorum will
be considered deprecated starting in 2.6. Our default connection mechanism
will switch to
