I won't pretend to be involved enough in the 2.0 work to give an opinion
:) -- I did say earlier that I'm happy to land this in 2.0 or 3.0
(whatever master decides to be at the time I merge).
If the spirit of the voters is to include this in 3.0 and not 2.0,
that's fine by me. I'm also happy
huaxiang sun created HBASE-18021:
Summary: Add more info in timed out RetriesExhaustedException for
read replica client get processing,
Key: HBASE-18021
URL: https://issues.apache.org/jira/browse/HBASE-18021
Would it help to cut a branch for 2.0 before attempting to merge in a new
major feature?
On Tue, May 9, 2017 at 8:41 AM, Josh Elser wrote:
> Reminder: I hope to close this in ~30hrs and there have been no votes so
> far.
>
>
> Josh Elser wrote:
>
>> Folks,
>>
>> This is a
Alex Leblang created HBASE-18020:
Summary: Update API Compliance Checker to Incorporate Improvements
Done in Hadoop
Key: HBASE-18020
URL: https://issues.apache.org/jira/browse/HBASE-18020
Project:
Chia-Ping Tsai created HBASE-18019:
--
Summary: Clear redundant memstore scanner
Key: HBASE-18019
URL: https://issues.apache.org/jira/browse/HBASE-18019
Project: HBase
Issue Type: Improvement
Umesh Agashe created HBASE-18018:
Summary: Support abort for all procedures by default
Key: HBASE-18018
URL: https://issues.apache.org/jira/browse/HBASE-18018
Project: HBase
Issue Type:
+1 on merging this to master branch.
I have reviewed Josh's work for phase 1.
This is an important addition for multi-tenant deployments.
On Fri, May 5, 2017 at 4:24 PM, Josh Elser wrote:
> Folks,
>
> This is a vote to (rebase and) merge the branch HBASE-16961 into master.
>
Reminder: I hope to close this in ~30hrs and there have been no votes so
far.
Josh Elser wrote:
Folks,
This is a vote to (rebase and) merge the branch HBASE-16961 into master.
Per the book, this requires 3 binding +1's from other committers to merge.
Relevant info for those who want to
[
https://issues.apache.org/jira/browse/HBASE-17999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved HBASE-17999.
Resolution: Invalid
Please ask questions on the user mailing list: u...@hbase.apache.org
>