[jira] [Resolved] (HBASE-18842) The hbase shell clone_snaphost command returns bad error message

[ https://issues.apache.org/jira/browse/HBASE-18842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey resolved HBASE-18842. - Resolution: Fixed Fix Version/s: 1.4.5 2.0.1 1.3.3

Re: [DISCUSS] Branching for HBase 1.5 and Hadoop minimum version update (to 2.7)

I'm in favour of 2.7.1+ as well. A special call-out about Hadoop also seems fine. Thanks Andrew! On Thu, Apr 26, 2018 at 8:42 AM Andrew Purtell wrote: > I think yes > > On Wed, Apr 25, 2018 at 7:13 AM, Sean Busbey wrote: > > > How would we rephrase our

Re: [DISCUSS] Branching for HBase 1.5 and Hadoop minimum version update (to 2.7)

I think yes On Wed, Apr 25, 2018 at 7:13 AM, Sean Busbey wrote: > How would we rephrase our compatibility guidelines? Special call-out > section about Hadoop? > > On Tue, Apr 24, 2018 at 10:37 PM, Andrew Purtell > wrote: > > Let's consider branching for

[jira] [Created] (HBASE-20494) Upgrade com.yammer.metrics dependency

Vlad Rozov created HBASE-20494: -- Summary: Upgrade com.yammer.metrics dependency Key: HBASE-20494 URL: https://issues.apache.org/jira/browse/HBASE-20494 Project: HBase Issue Type: Improvement

[jira] [Created] (HBASE-20493) Port HBASE-19994 (Create a new class for RPC throttling exception, make it retryable) to branch-1

Andrew Purtell created HBASE-20493: -- Summary: Port HBASE-19994 (Create a new class for RPC throttling exception, make it retryable) to branch-1 Key: HBASE-20493 URL:

[jira] [Reopened] (HBASE-9465) Push entries to peer clusters serially

[ https://issues.apache.org/jira/browse/HBASE-9465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell reopened HBASE-9465: --- > Push entries to peer clusters serially > -- > >

[jira] [Created] (HBASE-20492) UnassignProcedure is stuck in retry loop on region with state OPENING

Umesh Agashe created HBASE-20492: Summary: UnassignProcedure is stuck in retry loop on region with state OPENING Key: HBASE-20492 URL: https://issues.apache.org/jira/browse/HBASE-20492 Project: HBase

[development] How to get Client ID or Client Name from Get object in coprocessor implementation

Hi, I am trying to implement a coprocessor and one info I'd like to get is clientID or clientName for each Get op. I haven't found a place I can retrieve this. Is this possible? I am going to implement RegionObserver. The hook I refer to is this: void preGetOp(ObserverContext c, Get get, List

[jira] [Created] (HBASE-20491) Refactor our yetus plugins into a directory

Sean Busbey created HBASE-20491: --- Summary: Refactor our yetus plugins into a directory Key: HBASE-20491 URL: https://issues.apache.org/jira/browse/HBASE-20491 Project: HBase Issue Type: Task

Re: [DISCUSS] ruby-lint in precommit

+1 for the -0 ;) On 4/25/18 1:32 PM, Stack wrote: Agree. If we want to torture a contributor, we can set them on fixing all complaints. St.Ack On Wed, Apr 25, 2018 at 7:28 AM, Sean Busbey wrote: Hi folks! Given how often I see us ignoring ruby-lint feedback in

[jira] [Created] (HBASE-20490) Add main to UnsafeAvailChecker so can test for Unsafe

stack created HBASE-20490: - Summary: Add main to UnsafeAvailChecker so can test for Unsafe Key: HBASE-20490 URL: https://issues.apache.org/jira/browse/HBASE-20490 Project: HBase Issue Type: Bug

[jira] [Reopened] (HBASE-19924) hbase rpc throttling does not work for multi() with request count rater.

[ https://issues.apache.org/jira/browse/HBASE-19924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huaxiang sun reopened HBASE-19924: -- > hbase rpc throttling does not work for multi() with request count rater. >

[jira] [Created] (HBASE-20489) Update Reference Guide that CLUSTER_KEY value is present on the Master UI info page.

Sakthi created HBASE-20489: -- Summary: Update Reference Guide that CLUSTER_KEY value is present on the Master UI info page. Key: HBASE-20489 URL: https://issues.apache.org/jira/browse/HBASE-20489 Project:

Re: [VOTE] The third release candidate for HBASE 2.0.0 (RC2) is available

+1 Checked signatures : good Ran test suite with Java 8 : passed > On Wed, Apr 25, 2018 at 1:12 PM, Andrew Purtell > wrote: > > > +1 > > > > Checked sums and signatures: ok > > Built from source: ok (8u152) > > RAT check passes: ok (8u152) > > LTT 1M rows 20% updates: ok

Re: [DISCUSS] ruby-lint in precommit

Agree. If we want to torture a contributor, we can set them on fixing all complaints. St.Ack On Wed, Apr 25, 2018 at 7:28 AM, Sean Busbey wrote: > Hi folks! > > Given how often I see us ignoring ruby-lint feedback in precommit, > would anyone be opposed to me changing its

Re: Idle thoughts on tooling around maintaining older branches

I think we definitely need a tool like this! +1 On Wed, Apr 25, 2018 at 5:31 PM, Sean Busbey wrote: > I don't want to get stuck on the particulars of the specific jira, but > take as an example HBASE-18842 "The hbase shell clone_snaphost command > returns bad error message".

Idle thoughts on tooling around maintaining older branches

I don't want to get stuck on the particulars of the specific jira, but take as an example HBASE-18842 "The hbase shell clone_snaphost command returns bad error message". This issue was fixed back in October, but only for 3.0.0-SNAPSHOT. It looks to me like a good candidate for earlier branches

[jira] [Reopened] (HBASE-18842) The hbase shell clone_snaphost command returns bad error message

[ https://issues.apache.org/jira/browse/HBASE-18842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey reopened HBASE-18842: - > The hbase shell clone_snaphost command returns bad error message >

Re: [DISCUSS] ruby-lint in precommit

Yea, ruby lint is harsher than we need, I think. Letting it vote -0 SGTM. On Wed, Apr 25, 2018 at 9:28 AM, Sean Busbey wrote: > Hi folks! > > Given how often I see us ignoring ruby-lint feedback in precommit, > would anyone be opposed to me changing its vote from -1 to -0? >

[DISCUSS] ruby-lint in precommit

Hi folks! Given how often I see us ignoring ruby-lint feedback in precommit, would anyone be opposed to me changing its vote from -1 to -0? If someone eventually does the work to make it deal with e.g. jruby-isms and maven directory structure, we could then turn it back on. But I definitely

[jira] [Resolved] (HBASE-20388) nightly tests running on a feature branch should only comment on that feature branch's jira

[ https://issues.apache.org/jira/browse/HBASE-20388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey resolved HBASE-20388. - Resolution: Fixed Release Note: N.B. this issue only impacts developers working on

[jira] [Reopened] (HBASE-20388) nightly tests running on a feature branch should only comment on that feature branch's jira

[ https://issues.apache.org/jira/browse/HBASE-20388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey reopened HBASE-20388: - > nightly tests running on a feature branch should only comment on that feature > branch's jira >

Re: [DISCUSS] Branching for HBase 1.5 and Hadoop minimum version update (to 2.7)

How would we rephrase our compatibility guidelines? Special call-out section about Hadoop? On Tue, Apr 24, 2018 at 10:37 PM, Andrew Purtell wrote: > Let's consider branching for HBase 1.5. > > The new feature justifying a minor increment is storage class aware > placement

Re: [VOTE] The third release candidate for HBASE 2.0.0 (RC2) is available

Thanks Lars. S On Wed, Apr 25, 2018 at 1:28 AM, Lars Francke wrote: > Thanks Stack. > > In that case I'm -0 on this RC. > I'd really like to either revert that patch or at least document the > deprecation so we can remove it in 3.0. The way it is now we can't remove >

[jira] [Created] (HBASE-20488) PE tool prints full name in help message

Peter Somogyi created HBASE-20488: - Summary: PE tool prints full name in help message Key: HBASE-20488 URL: https://issues.apache.org/jira/browse/HBASE-20488 Project: HBase Issue Type:

[jira] [Created] (HBASE-20487) Sorting table regions by region name does not work on web UI

Balazs Meszaros created HBASE-20487: --- Summary: Sorting table regions by region name does not work on web UI Key: HBASE-20487 URL: https://issues.apache.org/jira/browse/HBASE-20487 Project: HBase

Re: [VOTE] The third release candidate for HBASE 2.0.0 (RC2) is available

Thanks Stack. In that case I'm -0 on this RC. I'd really like to either revert that patch or at least document the deprecation so we can remove it in 3.0. The way it is now we can't remove getTypeByte() in 3.0 because we'll need it for getType() which we can't change because it's not documented