[jira] [Created] (HBASE-23889) Switch back to ZKConnectionRegistry by default at least in test

Duo Zhang created HBASE-23889: - Summary: Switch back to ZKConnectionRegistry by default at least in test Key: HBASE-23889 URL: https://issues.apache.org/jira/browse/HBASE-23889 Project: HBase

Re: [DISCUSS] shade Jetty

Downstream users of hbase should be using our shaded testing until, which should already relocate jetty to avoid breaking out downstream users. On Mon, Feb 24, 2020, 19:42 张铎(Duo Zhang) wrote: > It is a bit sad that we have to shade jetty, as it is only used at server > side I think. > > But

Re: [DISCUSS] shade Jetty

It is a bit sad that we have to shade jetty, as it is only used at server side I think. But anyway, HBase also has a testing-util module which will pull jetty in, so we could also break our downstream users. +1 on shading. Josh Elser 于2020年2月25日周二 上午8:12写道： > Yeah, re-reading my previous

Re: [DISCUSS] shade Jetty

IIRC the test failures were because we don't use the client facing test artifact from Hadoop that shades its dependencies. I don't know if we _can_ use that dependency at the moment due to the number of places we have our hands into the internals of Hadoop. On Mon, Feb 24, 2020, 18:12 Josh Elser

Re: [DISCUSS] Drop support for code contribution via Jira attached patch

If it is not easy to add JDK11 support for the PreCommit-HBASE-Build job then I'm +1 with stopping it. We should make all the contribution ways have the same pre commit check. Nick Dimiduk 于2020年2月25日周二 上午7:33写道： > > The bot is for lots of projects, not only HBase, so we can not shut it > down.

Re: [DISCUSS] shade Jetty

Yeah, re-reading my previous chatter with MikeD and Appy, shading in hbase-thirdparty appears to have been the consensus. Best as I remember, time was the only reason it didn't happen. I don't think there's any reason we can't shade our use of Jetty, and just let Hadoop do what they do (and

Re: [DISCUSS] shade Jetty

Not sure about the real deployment, but the tests fail with NoSuchMethodError once they start a MiniDFSCluster. (as explained in HBASE-18943 ) I can verify this is still the case now. On Mon, Feb 24, 2020 at 3:53 PM Sean Busbey wrote: > As an

Re: [DISCUSS] shade Jetty

As an alternative, if we ensured the jetty from Hadoop wasn't in our classpath for our service roles would that allow us to version jetty independently? Or would we run into test problems? On Mon, Feb 24, 2020, 16:07 Wei-Chiu Chuang wrote: > Hi, > > While I work on this jira HBASE-23834 >

Re: [DISCUSS] shade Jetty

I am in favor of shading Jetty as well, if we can. The caveat being "if we can". On Mon, Feb 24, 2020 at 2:11 PM Wei-Chiu Chuang wrote: > Forgot to share a few past attempts: > >1. HBASE-18224 >Upgrade >jetty > > >1. HBASE-19390

Re: [DISCUSS] Drop support for code contribution via Jira attached patch

> The bot is for lots of projects, not only HBase, so we can not shut it down. Pardon me Duo. I am proposing we terminate PreCommit-HBASE-Build. The PreCommit-Admin job appears to be the responsibility of Yetus and is out of scope of my discussion here. > There's already debt on that job; Nick

[jira] [Reopened] (HBASE-22827) Expose multi-region merge in shell and Admin API

[ https://issues.apache.org/jira/browse/HBASE-22827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi reopened HBASE-22827: > Expose multi-region merge in shell and Admin API > > >

[jira] [Created] (HBASE-23888) PreCommit-HBASE-Build ignores the `ATTACHMENT_ID` provided by PreCommit-Admin

Nick Dimiduk created HBASE-23888: Summary: PreCommit-HBASE-Build ignores the `ATTACHMENT_ID` provided by PreCommit-Admin Key: HBASE-23888 URL: https://issues.apache.org/jira/browse/HBASE-23888

Re: [DISCUSS] shade Jetty

Forgot to share a few past attempts: 1. HBASE-18224 Upgrade jetty 1. HBASE-19390 Revert to older version of Jetty 9.3 1. HBASE-19256

[DISCUSS] shade Jetty

Hi, While I work on this jira HBASE-23834 (HBase fails to run on Hadoop 3.3.0/3.2.2/3.1.4 due to jetty version mismatch) and I realized this was attempted before. But it simply doesn't work when you have Hadoop and HBase on different Jetty minor

[jira] [Resolved] (HBASE-23755) [OpenTracing] Declare HTrace is unusable in the user doc

[ https://issues.apache.org/jira/browse/HBASE-23755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viraj Jasani resolved HBASE-23755. -- Fix Version/s: 2.1.10 2.2.4 2.3.0 Resolution:

[VOTE] First Release Candidate for HBase 1.6.0 is available for download

Please vote on this release candidate (RC0) for Apache HBase 1.6.0. The VOTE will remain open for at least 72 hours. The tag to be voted on is '1.6.0RC0' (5ec5a5b115), available for download at https://dist.apache.org/repos/dist/dev/hbase/1.6.0RC0/ Maven artifacts are available in a staging

Re: [VOTE] Merge "HBASE-22514 Move rsgroup feature into core of HBase" back to master

I'm currently -0. I left feedback on the merge PR with specifics. On Sat, Feb 22, 2020, 07:32 Duo Zhang wrote: > The issue aims to make rs group the first class citizen in HBase, where the > feature can be enabled through a simple flag, not a complicated > coprocessor, and also we can manage it

[VOTE] First Release Candidate for HBase 1.4.13 is available for download

Please vote on this release candidate (RC0) for Apache HBase 1.4.13. The VOTE will remain open for at least 72 hours. [ ] +1 Release this package as Apache HBase 1.4.13 [ ] -1 Do not release this package because ... The tag to be voted on is '1.4.13RC0' (38bf65a

[jira] [Created] (HBASE-23887) BlockCache performance improve

Danil Lipovoy created HBASE-23887: - Summary: BlockCache performance improve Key: HBASE-23887 URL: https://issues.apache.org/jira/browse/HBASE-23887 Project: HBase Issue Type: New Feature