[
https://issues.apache.org/jira/browse/HBASE-21891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nihal Jain resolved HBASE-21891.
Resolution: Duplicate
Based on [~a00408367]
Subrat Mishra created HBASE-22116:
-
Summary: HttpDoAsClient to support keytab and principal in command
line argument.
Key: HBASE-22116
URL: https://issues.apache.org/jira/browse/HBASE-22116
Project:
[
https://issues.apache.org/jira/browse/HBASE-21886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang reopened HBASE-21886:
Reopen for run ITBLL again for 2.2.0RC1.
> Run ITBLL for branch-2.2
>
On Tue, Mar 26, 2019 at 5:04 PM Sean Busbey wrote:
> ...
>
> > I didn't mention this issue in the 2.1.4 announcement. I can add a
> > follow-on or maybe better, add note on download page?
> >
>
> Download page seems more likely to catch an eye I think.
>
Added a 'notices' column to downloads
Sergey Shelukhin created HBASE-22115:
Summary: HBase RPC aspires to grow an infinite tree of trace scopes
Key: HBASE-22115
URL: https://issues.apache.org/jira/browse/HBASE-22115
Project: HBase
Andrew Purtell created HBASE-22114:
--
Summary: Port HBASE-15560 (TinyLFU-based BlockCache) to branch-1
Key: HBASE-22114
URL: https://issues.apache.org/jira/browse/HBASE-22114
Project: HBase
On Tue, Mar 26, 2019 at 3:59 PM Stack wrote:
>
> On Tue, Mar 26, 2019 at 9:31 AM Sean Busbey wrote:
>
> > Wait so are the shaded clients busted in 2.1.4? The release note on
> > HBASE-22052 doesn't clearly state this, and I would expect folks
> > looking to upgrade would want to know.
> >
> >
>
[
https://issues.apache.org/jira/browse/HBASE-21728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-21728.
Resolution: Fixed
> Backport to branch-2 (and maybe branch-1) HBASE-21684 Throw DNRIOE
On Tue, Mar 26, 2019 at 9:31 AM Sean Busbey wrote:
> Wait so are the shaded clients busted in 2.1.4? The release note on
> HBASE-22052 doesn't clearly state this, and I would expect folks
> looking to upgrade would want to know.
>
>
The nightly test was failing, yes. Fix didn't make 2.1.4 (It
[
https://issues.apache.org/jira/browse/HBASE-21752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xu Cang resolved HBASE-21752.
-
Resolution: Won't Fix
> Backport getProcedures() to branch-1 from branch-2 in HMaster class
>
[
https://issues.apache.org/jira/browse/HBASE-21846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xu Cang resolved HBASE-21846.
-
Resolution: Resolved
Release Note: test is not flaky anymore after the revert
> Flaky Test:
Simon poortman created HBASE-22113:
--
Summary: HBASE S. Poortman
Key: HBASE-22113
URL: https://issues.apache.org/jira/browse/HBASE-22113
Project: HBase
Issue Type: Improvement
Simon poortman created HBASE-22112:
--
Summary: S. Poortman
Key: HBASE-22112
URL: https://issues.apache.org/jira/browse/HBASE-22112
Project: HBase
Issue Type: New Feature
Simon poortman created HBASE-22111:
--
Summary: 19-88
Key: HBASE-22111
URL: https://issues.apache.org/jira/browse/HBASE-22111
Project: HBase
Issue Type: New Feature
Reporter:
Simon poortman created HBASE-22110:
--
Summary: HBASE (S. Poortman)
Key: HBASE-22110
URL: https://issues.apache.org/jira/browse/HBASE-22110
Project: HBase
Issue Type: Bug
Gabor Bota created HBASE-22109:
--
Summary: Update hbase shaded content checker after guava update in
hadoop branch-3.0 to 27.0-jre
Key: HBASE-22109
URL: https://issues.apache.org/jira/browse/HBASE-22109
[
https://issues.apache.org/jira/browse/HBASE-21968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-21968.
---
Resolution: Fixed
Fix Version/s: 2.1.4
HBASE-22052 is a problem but 2.1.4RC1 vote passed... Let me
[
https://issues.apache.org/jira/browse/HBASE-21802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-21802.
---
Resolution: Fixed
Announcement sent. Resolving
> Release 2.0.5
> -
>
> Key:
The HBase team is happy to announce the immediate availability of Apache
HBase 2.1.4.
Download from https://hbase.apache.org/downloads.html
Apache HBase is an open-source, distributed, versioned, non-relational
database. Apache HBase gives you low latency random access to billions of
rows with
The HBase team is happy to announce the immediate availability of Apache
HBase 2.0.5.
NOTICE: We plan on this being the last release on branch-2.0 (unless
critical issues found).
Download from https://hbase.apache.org/downloads.html
Apache HBase is an open-source, distributed, versioned,
Wait so are the shaded clients busted in 2.1.4? The release note on
HBASE-22052 doesn't clearly state this, and I would expect folks
looking to upgrade would want to know.
On Mon, Mar 25, 2019 at 8:53 AM Stack wrote:
>
> With 5 +1s, this RC passes. Thanks to all who voted! Let me push out this
>
Thanks Duo for vote.
Vote passes with 6 +1s.
Thanks to all who voted.
Let me push out this release,
S
On Tue, Mar 26, 2019 at 3:58 AM 张铎(Duo Zhang) wrote:
> +1(binding), but please upload the compatibility report sir.
>
> Built from src: OK
> Checked sums & sigs: All matched
> Rat check: OK
Issue is fixed and the new job succeeded.
On Tue, Mar 26, 2019 at 3:34 PM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:
> Build status: Failure
>
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
>
> See
Build status: Failure
The HBase website has not been updated to incorporate HBase commit
${CURRENT_HBASE_COMMIT}.
See https://builds.apache.org/job/hbase_generate_website/1627/console
Yep, the trigger to call Jenkins from Github PR's is something Infra
controls. All I know is that I sent an email to us...@infra.apache.org
explaining what I was trying to do, and an Infra team member said they
"enabled two options" for me and then everything worked.
Hopefully, if you just
OK, sounds reasonable.
Thanks.
Sean Busbey 于2019年3月26日周二 下午6:13写道：
> If it's all messages, probably to whatever all jira notifications go to.
>
> Iirc, issue creation and closing on jira goes to dev@ so the equivalent
> for
> PRs is fine imho.
>
> On Mon, Mar 25, 2019, 21:30 张铎(Duo Zhang)
If it's all messages, probably to whatever all jira notifications go to.
Iirc, issue creation and closing on jira goes to dev@ so the equivalent for
PRs is fine imho.
On Mon, Mar 25, 2019, 21:30 张铎(Duo Zhang) wrote:
> Oh, an email to the dev list...
>
> It will be better to send this to
+1(binding), but please upload the compatibility report sir.
Built from src: OK
Checked sums & sigs: All matched
Rat check: OK
Run all UTs(openjdk8u202):
TestHBaseTestingUtility.testMiniZooKeeperWithMultipleClientPorts fails with
-PrunAllTests, but I think this is a known issue, it will be fine
28 matches
Mail list logo
