I sent an invitation.
On Sun, Feb 17, 2019 at 2:32 PM zheng wang <18031...@qq.com> wrote:
> Dear HBase community,
>
>
> I have some questions regarding how to contribute bug fixes. Since it is
> easier to communicate in realtime I would like to join the HBase Slack
> channel, so I am writing to
+1
Signature, checksum: OK
Build from source: OK
Unit tests: OK
Rat check: OK
Start in standalone mode: OK
LTT 1M rows: OK
Shell basic commands: OK
On Sat, Feb 16, 2019 at 3:32 AM Sean Busbey wrote:
> The first release candidate for HBase 1.2.11 is available for download:
>
>
+1 (binding)
Checked signatures, checksums: ok
Apache Rat check: ok
Build source: ok (jdk1.8.0_201)
Unit tests: ok
LTT 1M rows: ok
Run in pseudo distributed mode: ok (Hadoop 2.7.7)
Shell basic commands: ok
Web UI: ok
Tested RS Group: ok
On Tue, Feb 12, 2019 at 7:48 AM Guanghao Zhang wrote:
>
A pull request was just merged to hbase-site repo while this build was
running so it failed to push changes. Restarted the job now.
On Tue, Feb 12, 2019 at 3:47 PM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:
> Build status: Failure
>
> The HBase website has not been updated to
ugh plan so we can
> help spot problems. :)
>
> Misty
>
> On Tue, Feb 5, 2019 at 4:44 AM Peter Somogyi wrote:
>
> > That's a very good point Nick!
> >
> > I'd know how we could add rel=canonical tag to 0.94 pages if we remove
> > those. Also, how could we add
Dear HBase Community,
The documentation of Apache HBase 0.94 release was removed from
https://hbase.apache.org/ website.
In case you still need it you can download the latest 0.94 release tarball
from https://archive.apache.org/dist/hbase/hbase-0.94.27/ which contains
the rendered documentation
Just like Xu Cang I ran into similar test failures on Debian and many of
these are on the flaky list for branch-1 with 100% flakyness.
https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-1/lastSuccessfulBuild/artifact/dashboard.html
These are the failed tests for
ocs. I don't know why the SEO lands us thusly, but I fear that
> > > suddenly it'll look to user searches like the project is dead.
> > >
> > > On Mon, Feb 4, 2019 at 11:46 AM Misty Linville
> wrote:
> > >
> > > > +1
> > > >
> >
Does anyone have any concern with removing 0.94 documentation completely
from hbase.apache.org? Currently it is hosted at
https://hbase.apache.org/0.94/ to which we don't have any direct link but
with a few hops a user can reach this area. This release is almost 4 years
old!
I had a chat with
Thanks for checking on this William!
Stack and I are working on this issue on HBASE-2, it is caused by the
protobuf upgrade in hbase-thirdparty.
Peter
On 2019/04/12 20:42:56, William Shen wrote:
> Sorry, one step behind in my inbox. Seems like discussion is ongoing in
>
+1
Signature, checksum: OK
Apache RAT: OK
Build from source: OK
Unit tests: OK
LTT 1M rows: OK
Basic shell commands: OK
On 2019/04/07 19:02:58, Sean Busbey wrote:
> The first release candidate for HBase 1.2.12 is available for download:
>
>
gt;
> On Fri, May 10, 2019 at 6:18 AM 张铎(Duo Zhang)
> wrote:
>
> > +1.
> >
> > Jan Hentschel 于2019年5月10日周五 下午9:08写道：
> >
> > > Also +1 for making it IA.Private.
> > >
> > > From: Peter Somogyi
> > > Reply-To: "dev@hbase.ap
e
> addendum to branch-2.2 and rolled 2.2.0RC4..
>
> 张铎(Duo Zhang) 于2019年5月26日周日 上午10:39写道：
>
> > So we need to roll new RCs for both 2.1.5 and 2.2.0?
> >
> > Peter Somogyi 于2019年5月26日 周日05:46写道：
> >
> > > Apologies, I misinterpreted git log and JIRA pre
issue, which just changes the
> annotation for branch-2.2-, and commit the addendum again, with a new
> commit message.
>
> Peter Somogyi 于2019年5月25日 周六16:42写道：
>
> > On the 2.1.5RC0 testing I noticed that the release notes do not state
> that
> > LossyCounting was moved
res. For your consideration.
>
> > On May 25, 2019, at 12:37 PM, Peter Somogyi
> wrote:
> >
> > Unfortunately, that would require a new RC for 2.1.5 and I'm afraid
> > Guanghao already started the process for 2.0.0.
> >
> > On Sat, May 25, 2019 at 12:
On behalf of the HBase PMC, I'm pleased to announce that Wellington
Chevreuil has accepted our invitation to become an HBase committer.
Thanks for all your hard work Wellington; we look forward to more
contributions!
Please join me in extending congratulations to Wellington!
+1
Checked:
- Signature, checksum
- Build from source
- Rat check
- Unit tests
- Basic shell commands
- LTT 1M rows
On Fri, Jun 7, 2019 at 2:09 PM Artem Ervits wrote:
> +1 (non-binding)
>
> -Tested with "hbase-vote.sh -s
> https://dist.apache.org/repos/dist/dev/hbase/1.4.10RC1/; --output-dir
>
FYI: The dist.a.o link is incorrect in the email, it does not have hbase-
prefix before the version.
Use https://dist.apache.org/repos/dist/dev/hbase/1.4.10RC1/
1.3.5RC0 is similar.
On Thu, Jun 6, 2019 at 2:11 AM Andrew Purtell wrote:
> The second HBase 1.4.10 release candidate (RC1) is
+1
Signature, checksum: ok
Apache Rat check: ok
Build from source: ok
Unit tests: ok (2 failures but rerun was successful)
LTT 1m rows: ok
Web UIs: ok
Basic shell commands: ok
Release notes, changes: ok
On Thu, May 30, 2019 at 6:33 PM Artem Ervits wrote:
> +1 non-binding
> using hbase-vote
sh you need within git to reproduce a build problem.
> > > >>>>
> > > >>>> On Mon, Jun 10, 2019 at 2:26 PM Josh Elser
> > wrote:
> > > >>>>
> > > >>>>> https://issues.apache.org/jira/browse/HBASE-22563 for a quic
Hi,
HBase jobs are using more than 400GB based on this list.
Could someone take a look at the job configurations today? Otherwise, I
will look into it tomorrow morning.
Thanks,
Peter
-- Forwarded message -
From: Chris Lambertus
Date: Mon, Jun 10, 2019 at 7:57 PM
Subject: ACTION
l need
> > to be more specific. I can only guess what you are looking at.
> >
> > Currently this veto is not valid because it does not indicate what the
> > actual problem is. Please file a JIRA with your instructions to remedy
> the
> > problem. At the very least
-1
Compatibility report shows removed methods and changed constructor
signature for a IA.Public interface. There are also a couple of changes for
IA.LP classes.
Also checked:
Checksum, signature OK
Rat check OK
Unit tests OK
Simple shell commands OK
LTT 1M rows OK
Master, RS UI OK
On Sat, May
+1 on moving LossyCounting to IA.Private
On Fri, May 10, 2019 at 7:54 AM Stack wrote:
> Looks good to me.
> S
>
> On Thu, May 9, 2019 at 7:02 PM Sean Busbey wrote:
>
> > Hi folks!
> >
> > just a heads up that a few of us are planning to move a class out of
> > the public API without a
+1
signatures, checksums: OK
build from source: OK (Oracle 1.8.0_171, Maven 3.6.1)
Apache rat check: OK
Unit / IT tests: OK
Filed issues for Josh's and Artem's findings:
HBASE-22336
HBASE-22337
HBASE-22338
On Mon, Apr 29, 2019 at 7:07 PM Artem Ervits wrote:
> +1 (non-binding)
>
> signatures
> The committer then has control over the
commit message, though it does break things into a "subject" box and a
"body" box. the subject is placed first in the message followed by two
newlines and then the body.
I just double checked this on PR 181, it gives 2 boxes for commit message:
title and
The committer has full control over commit message on squash commits. By
default, it will use PR title for first row and list of commit messages in
the commit message description.
I prefer multiple commits in a single PR compared to force pushing to
feature branch because it makes incremental
Some clarification to my previous email after reading the reply from Sean.
I meant to squash multiple commits into a single one when the pull request
touches a single JIRA.
As an example this could be submitted using squash and merge:
Pull Request: HBASE-
Commit 1: HBASE-
Commit 2:
> How to we weigh these competing concerns?
When a contributor adds multiple commits to a pull request we can use
"Squash and merge". Therefore the pull request will land on the target
branch as a single commit which can be cherry-picked to other branches as
we did previously.
On Tue, Apr 23,
+1 (with note)
Checked signature, checksum
Built from source on 2.2.1RC0 tag
Built HBase master branch with HBASE-2 patch applied.
NOTE:
The CHANGES.md file marks 2.2.0 as unreleased.
"Release thirdparty-2.2.0 - Unreleased (as of 2019-03-30)"
Thanks,
Peter
On Tue, Apr 16, 2019 at 6:12 PM
+1
Questionable:
* Compatibility report: Should be fine? There are some compatibility issues
reported with MultiRowRangeFilter bit it doesn't seem to be an issue for
me. This was already released with 2.1.5.
* Signature, checksum: ok
* Rat check: ok
* Unit tests: ok (some mapreduce tests failed,
+1
* Signature, checksum: ok
* Rat check: ok
* Unit tests: ok
* Compatibility report: ok
* Release notes, changes: ok
* LTT 1M rows: ok
* Basic shell commands in standalone mode: ok
On Wed, Aug 14, 2019 at 5:15 PM Duo Zhang wrote:
> The first release candidate for HBase 2.1.6 is available for
an hbck2 alpha
> > release?
> > >> > > > I'm fine with an alpha release but since "HBCK2 should
> > continuously
> > >> > > evolve"
> > >> > > > it might be better to always use the latest codebase whenever
> you
&
+1
Signature, checksum: OK
Rat check: OK
Build from source: OK
Unit tests: OK
LTT 1M rows, standalone mode: OK
Changes, Release Notes: OK
Compatibility Report: OK
On Thu, Aug 29, 2019 at 2:22 AM Sakthi wrote:
> *+1 (Non-Binding)*
>
> Java Version - java-1.8.0-amazon-corretto-jdk_8.222.10-1
>
>
Hi everyone,
This topic came up a couple of times already but now we reached a point
when the recent HBCK2 is incompatible with older HBase releases,
specifically 2.0.x, 2.1.0 and 2.1.1. When you build HBCK2 against one of
the previously mentioned releases you will get compilation errors. (mvn
one HBCK2 release as the goal.
> >
> > Is it possible to put some hacks into HBCK2 to work around the
> > compatibility to fix the current state and focus more on automation to
> > let us know the next time we inevitably break it again? ;)
> >
> > On 8/29/19
gt; > the ones from hbck1, I guess a first release would provide a working
> > hbck2
> > > that already brings a considerable number of fix methods to help with
> > most
> > > common inconsistencies issues seen in hbase 2 so far. And we could
> still
> >
Hi,
I agree with Nick, feel free to create a feature branch if that makes your
testing easier.
One thing that I'd like to add is if you do not want to have nightly and
flaky test to runs on this branch (probably this is the case for this
specific feature branch) then you should remove the
This is scary. Thanks Duo for monitoring the issue!
On Wed, Sep 4, 2019 at 1:09 PM 张铎(Duo Zhang) wrote:
> As well as the nightly and flaky jobs.
>
> As all the nodes under hadoop label on jenkins are dead...
>
> https://builds.apache.org/label/Hadoop/
>
> Please keep an eye here
>
>
Hi,
The problem is the same that was fixed in HBASE-22981 for the nightly jobs.
Yetus 0.11.0 fails the build in case there are unprocessed parameters. We
need to handle --skip-errorprone flag properly on branch-1s or
add --ignore-unknown-options=true to the Jenkinsfile in use.
Peter
On Wed, Sep
+1 (binding)
checked signature, checksum
verified version is correct in the bin tarball
On Tue, Sep 10, 2019 at 4:40 PM 张铎(Duo Zhang) wrote:
> +1(binding)
>
> Since the RC2 tag is at the same commit with RC1, I will carry the vote for
> RC1 here.
>
> And download the tarball and checked the
Yes, only test issue. RC is not affected.
On Mon, Sep 9, 2019 at 11:41 AM 张铎(Duo Zhang) wrote:
> Seems to be a UT issue? I do not think it is sufficient to sink an RC?
>
> OpenInx 于2019年9月9日周一 下午4:35写道：
>
> > Seems the TestHRegionWithInMemoryFlush is always failed under my host,
> > filed
as mentioned before but not production issues
- Shell simple commands: OK
- LTT 1M rows: OK
On Mon, Sep 9, 2019 at 11:56 AM OpenInx wrote:
> Agree, give my +1 (binding).
> BTW Peter Somogyi also have commit the fix to related branches.
> Thanks.
>
> On Mon, Sep 9, 2019 at 5:40
Please vote on this Apache HBase Operator Tools Release Candidate (RC),
1.0.0.
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache HBase Operator Tools 1.0.0
[ ] -1 Do not release this package because ...
The tag to be voted on is 1.0.0RC0:
for site and
> > documentation from the main repo to others for a while. Let’s continue
> > doing that. So probably the big hbtop readme and associated resources
> > should go into the online book and the docs in the source tree should
> refer
> > to the new book section
Hi,
Recently the hbtop tool (HBASE-11062) was merged and it also includes a
nice README documentation with demos in GIF format.
Although I think we should have more documentation like this, probably it
is not a good idea to store the images in the source repository. The size
of these GIF images
Congratulations!
On Mon, Aug 5, 2019 at 8:57 AM Pankaj kr wrote:
> Congratulations Zheng..!!
>
> Regards,
> Pankaj
>
> -Original Message-
> From: Duo Zhang [mailto:zhang...@apache.org]
> Sent: 05 August 2019 07:38
> To: HBase Dev List ; hbase-user <
> u...@hbase.apache.org>
> Subject:
at 18:42, Nick Dimiduk wrote:
> +1
>
> - Verified signatures.
> - Verified checksums.
> - Built from source tarball successfully.
> - Ran unit tests from source tarball, pass.
> - Ran rat check from source tarball, pass.
>
>
> On Mon, Sep 16, 2019 at 11:31 AM Peter
Yes, HBASE-23039.
Ok, I’m cancelling this RC0 and will roll RC1 soon.
Thanks,
Peter
On 2019. Sep 19., Thu at 15:16, 张铎(Duo Zhang) wrote:
> You mean HBASE-23039? Since this is a fresh new release, we'd better make
> it clean? I prefer we roll a new RC.
>
> Thanks.
>
> Peter S
+0
Checksum, signature: OK
CHANGES: OK
Build from source: OK
Rat check: OK
Build HBase master using hbase-thirdparty-3.1.0: OK
RELEASENOTES: NOK -> hbase-thirdparty-3.1.0 is duplicated. Please check
https://github.com/apache/hbase-operator-tools/pull/35
On Mon, Sep 30, 2019 at 8:07 PM Stack
ignatures and checksum: ok
> > > CHANGES and RELEASENOTES: ok
> > >
> > > Stack 于2019年9月21日周六 上午8:32写道：
> > >
> > > > +1
> > > >
> > > > Signatures and hash are good.
> > > > CHANGES and RELEASENOTES look complete.
With 3 binding and 4 non-binding +1s and no votes against, this vote passes.
Let me push out RC1 as release HBase Operator Tools 1.0.0.
Thanks to all who voted,
Peter
On Tue, Sep 24, 2019 at 10:28 AM Peter Somogyi wrote:
> +1
>
> Checked signatures, checksums
> Ran rat check
+1
Signature, checksum: OK
Build from source: OK
Rat check: OK
Use hbase-shaded-gson dependency in a project: OK
Changes, release notes: OK (only contains 3.0.0 content but I think we
don't need history)
On Sun, Sep 22, 2019 at 7:17 AM Sean Busbey wrote:
> Please consider the following for
+1
Signature, checksum: ok
Changes, release notes: ok
Rat check: ok
Build from source: ok
Build HBase with hbase-thirdparty 3.1.0: ok
On Tue, Oct 1, 2019 at 10:04 PM Stack wrote:
> Please vote on this Apache hbase thirdparty release candidate,
> hbase-thirdparty-3.1.0RC2
>
> The VOTE will
The HBase team is happy to announce the immediate availability of Apache
HBase Operator Tools 1.0.0.
Apache HBase™ Operator Tools provides HBCK2 which is the repair tool for
Apache HBase 2 clusters.
To learn more about HBase and HBase Operator Tools, see
https://hbase.apache.org/.
Apache HBase
+1
Another issue with ReviewBoard is that it requires Apache ID so only
committers are able to create new reviews or even comment.
On Wed, Nov 13, 2019 at 5:21 PM Nick Dimiduk wrote:
> Heya,
>
> Seems in the old days we were explicitly non-strict about where code review
> were happening. I
Sounds good!
I'd prefer to run HBCK against 2.2 latest version since that is planned to
get the stable pointer soon. It is also fine to run the test for 2.1 and
2.2 HBase versions.
Currently there is only a Yetus based pre-commit job for
hbase-operator-tools. Similarly to the main HBase
Congratulations Wellington!
On Thu, Oct 24, 2019 at 8:47 AM Balazs Meszaros
wrote:
> Congratulations Wellington!
>
> On Thu, Oct 24, 2019 at 4:56 AM 张铎(Duo Zhang)
> wrote:
>
> > Congratulations!
> >
> > Zach York 于2019年10月24日周四 上午7:28写道：
> >
> > > Welcome Wellington! Congratulations!
> > >
>
Congratulations Sakthi!
On Thu, Oct 24, 2019 at 8:56 AM Balazs Meszaros
wrote:
> Congratulations Sakthi!
>
> On Thu, Oct 24, 2019 at 5:06 AM 张铎(Duo Zhang)
> wrote:
>
> > Congratulations!
> >
> > Zach York 于2019年10月24日周四 上午7:51写道：
> >
> > > Welcome Sakthi! Congratulations!
> > >
> > > On Wed,
+1 (binding)
Signature, checksum: ok
Rat check: ok
Build from source: ok
Unit tests: ok
LTT 1M rows: ok
Shell basic commands: ok
On Thu, Oct 17, 2019 at 10:07 AM Sean Busbey wrote:
> +1 (binding)
>
> basics: rat, signatures, checksum, spot check license, compat report makes
> sense, checked
+1 for EOM
On Mon, Dec 2, 2019, 10:57 Jan Hentschel
wrote:
> +1
>
> From: Sakthi
> Reply-To: "dev@hbase.apache.org"
> Date: Monday, December 2, 2019 at 3:32 AM
> To: "dev@hbase.apache.org"
> Subject: Re: [DISCUSS] EOM branch-1.3
>
> +1
>
> On Sun, Dec 1, 2019 at 6:28 PM Andrew Purtell
Please vote on this Apache HBase Operator Tools Release Candidate (RC),
1.0.0.
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache HBase Operator Tools 1.0.0
[ ] -1 Do not release this package because ...
The tag to be voted on is 1.0.0RC1:
that can build an RC for all of them not worth the trouble? At the very
> > > least, I think the hbase-vote.sh can be made to work with releases
> > > generated from each of the repos, as it's not doing all that much.
> > >
> > > Thoughts?
> > >
&g
+1
Checksum: ok
Signature: ok
Build from source: ok
Rat check: ok
On Sun, Oct 6, 2019 at 7:02 AM Stack wrote:
> On Sat, Oct 5, 2019 at 5:34 AM 张铎(Duo Zhang)
> wrote:
>
> > +1(binding)
> >
> > Verified sigs and sums: Matched
> > Built hbase with the staging repo: Passed. See
> >
> >
>
+1
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_202): ok
- mvn clean apache-rat:check
* Built from source (1.8.0_202): ok
- mvn clean install -DskipTests
* Unit tests pass (1.8.0_202): ok
- mvn package -P runAllTests
* Releasenotes: ok
* Changes: ok
* API compat report: ok
* Start in
+1
Checked signature, checksum, CHANGES, RELEASENOTES
Build from src
Ran Apache Rat check
On Wed, Oct 9, 2019 at 10:03 AM 张铎(Duo Zhang) wrote:
> +1
>
> Stack 于2019年10月9日周三 上午4:58写道：
>
> > +1
> >
> > Checked sig and hashes, RELEASENOTES and CHANGES.
> >
> > Also ran through the test described
Probably when I built HBase using hbase-thirdparty 3.1.0 it used RC1’s
artifacts from my local maven cache. I’ll clean m2 cache next time before
voting.
On Fri, Oct 4, 2019 at 4:34 PM 张铎(Duo Zhang) wrote:
> The staging repo should be
>
>
+1 (binding)
Signature, checksum: ok
Rat check: ok
Build from source: ok
Unit tests: ok
LTT 1M rows: ok
Basic shell commands: ok
On Fri, Feb 28, 2020 at 12:15 AM Jan Hentschel <
jan.hentsc...@ultratendency.com> wrote:
> +1 (binding)
>
> * Signature: ok
> * Checksum : ok
> * Rat check
+1 (binding)
Signatures: ok
Checksums: ok
Rat check: ok
Built from source: ok
Unit tests: ok
Failed TestMasterBalanceThrottling, TestAdmin2,
TestReplicationKillSlaveRS but multiple reruns were successful
Compatibility report: ok
Start in standalone mode: ok
Web UI: ok
LTT 1M rows: ok
Peter
Thanks for the RC Stack!
I can't find the artifacts on the staging repository. The URL also
looks odd with the double / at the end.
Peter
On Thu, Jan 23, 2020 at 2:56 AM Stack wrote:
>
> Please vote on this Apache hbase thirdparty release candidate,
> hbase-thirdparty-3.2.0RC0
>
> The VOTE will
+1
checksum and signature
compared tar.gz with 3.2.0RC0 tag
built from source
built and tested branch-2 using 3.2.0RC0
(https://github.com/apache/hbase/pull/1086)
Peter
On Sat, Jan 25, 2020 at 12:35 AM Sean Busbey wrote:
>
> +1 (binding)
>
> On Wed, Jan 22, 2020 at 7:56 PM Stack wrote:
> >
>
On behalf of the Apache HBase PMC I am pleased to announce that
Viraj Jasani has accepted the PMC's invitation to become a
commiter on the project.
Thanks so much for the work you've been contributing. We look forward
to your continued involvement.
Congratulations and welcome!
Please vote on this Apache hbase thirdparty release candidate,
hbase-thirdparty-3.3.0RC0
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache hbase thirdparty 3.3.0
[ ] -1 Do not release this package because ...
The tag to be voted on is 3.3.0RC0:
like
> until a couple hours after we get 3 binding +1s)
>
> On Sat, Apr 25, 2020 at 9:58 AM Peter Somogyi wrote:
>
> > Please vote on this Apache hbase thirdparty release candidate,
> > hbase-thirdparty-3.3.0RC0
> >
> > The VOTE will remain open for at least 72 hour
Please vote on this Apache hbase thirdparty release candidate,
hbase-thirdparty-3.3.0RC1
The second release candidate only differs in the RELEASENOTES.md update
compared to RC0.
The VOTE will remain open until there are at least the required voting
majority
[ ] +1 Release this package as Apache
The hbase-thirdparty 3.3.0RC1 vote is up. The only difference is the update
in RELEASENOTE.md.
For reference see HBASE-24279.
Thanks,
Peter
On Tue, Apr 28, 2020 at 7:06 PM Peter Somogyi wrote:
> I'm rolling a new RC now with changing the RELEASENOTES only.
>
> On Tue, Apr 28, 2020 a
We've just made a new release of the Apache HBase Thirdparty project.
This project is used by the Apache HBase project to encapsulate a
number of core dependencies that HBase relies upon ensuring
that they are properly isolated from HBase downstream users, e.g.
Google Protocol Buffers, Google
4.1.44.Final
> protobuf: 3.9.2 =\> 3.11.1
> maven-assembly-plugin: 3.1.1 =\> 3.2.0
>
>
> Actually we reverted gson back to 2.8.5, and now the release note on jira
> is
>
> guava: 28.1-jre => 28.2-jre
> error_prone: 2.3.3 => 2.3.4
> netty: 4.1.42.Final => 4.1.4
+1 from me as well.
With five +1 votes (four binding), this vote passes. Let me push out the
release.
Thank you all for vote!
Peter
On Wed, Apr 29, 2020 at 1:52 PM Josh Elser wrote:
> +1 (binding)
>
> On Tue, Apr 28, 2020, 14:10 Peter Somogyi wrote:
>
> > Please vote on
That's great!
Do we need to do the same for the other repositories?
On Tue, May 5, 2020 at 12:03 AM Stack wrote:
> Good stuff Bharath,
> S
>
> On Mon, May 4, 2020 at 12:48 PM Bharath Vissapragada
> wrote:
>
> > Hi,
> >
> > I just committed this change
> > <
> >
>
Congratulations Wei-Chiu!
On Thu, May 14, 2020 at 7:59 AM 李响 wrote:
> Congratulations Wei-Chiu!
>
> On Thu, May 14, 2020 at 9:05 AM Hui Fei wrote:
>
> > Congratulations Wei-Chiu!
> >
> > Sean Busbey 于2020年5月14日周四 上午3:10写道：
> >
> > > Folks,
> > >
> > > On behalf of the Apache HBase PMC I am
Invitation sent.
On Wed, May 20, 2020 at 1:17 PM Nand kishor Bansal
wrote:
> Hi,
>
> I would like to join slack channel for hbase. Can somebody please send me
> an invite.
>
> Thanks,
> Nand
>
Congratulations!
On Tue, Oct 6, 2020 at 9:19 AM Balazs Meszaros wrote:
> Congratulations, Viraj!
>
> On Tue, Oct 6, 2020 at 4:48 AM Sukumar Maddineni
> wrote:
>
> > Wow Congrats Viraj, Keep it up..
> >
> > --
> > Sukumar
> >
> > On Mon, Oct 5, 2020 at 8:40 PM Sakthi wrote:
> >
> > > Congrats
+1 (binding)
signature, checksum: ok
changes, release notes: ok
tarball matches with 3.4.0RC2 tag: ok
build HBase master using # PR: ok
On Mon, Aug 17, 2020 at 10:04 AM 张铎(Duo Zhang)
wrote:
> Please vote on this Apache hbase thirdparty release candidate,
> hbase-thirdparty-3.4.0RC2
>
> The
+1 (binding)
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_265): ok
- mvn clean apache-rat:check
* Built from source (1.8.0_265): ok
- mvn clean install -DskipTests
* Unit tests pass (1.8.0_265): ok
- mvn package -P runAllTests
* LTT 1M rows: ok
* Changes, release notes: ok
On
The branch-2.1 reached End of Life so the builds got disabled. The last
release from branch-2.1 is 2.1.10.
On Wed, May 20, 2020 at 9:48 AM ramkrishna vasudevan <
ramkrishna.s.vasude...@gmail.com> wrote:
> Hi All
>
> After we did some recent checkins for branch-2.1 and was waiting for the
>
Big +1!
On Tue, Aug 11, 2020 at 10:02 AM 张铎(Duo Zhang)
wrote:
> The last release for 1.3.x is 2019.10.20, which means we do not have a
> release for this release line for about 10 months.
>
> Let's make it EOL and tell users to at least upgrade to 1.4.x?
>
> Thanks.
>
+1 (binding) with note
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_252): ok
- mvn clean apache-rat:check
* Built from source (1.8.0_252): ok
- mvn clean install -DskipTests
* Unit tests pass (1.8.0_252): ok
- mvn package -P
+1 (binding)
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_252): ok
- mvn clean apache-rat:check
* Built from source (1.8.0_252): ok
- mvn clean install -DskipTests
* Unit tests pass (1.8.0_252): ok
- mvn package -P runAllTests
* LTT 1M rows write: ok
* Simple shell operations: ok
*
+1 (binding)
Signatures & checksums: ok
Changes, release notes: ok
Compatibility report: ok
Rat check: ok
Built from source: ok
Unit test: ok
Shell basic commands: ok
LTT 1M rows: ok
On Mon, Jul 20, 2020 at 5:24 AM Guanghao Zhang wrote:
> Please vote on this release candidate (RC) for Apache
Sent invitation.
On Tue, Jul 21, 2020 at 4:52 PM Laxman Goswami
wrote:
>
>
+1 (binding)
* Changes, release notes: ok
* Basic shell commands: ok
* LTT 1M rows: ok
* UI: ok
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_242): ok
- mvn clean apache-rat:check "-D hadoop.profile=3.0"
* Built from source (1.8.0_242): ok
- mvn clean install -DskipTests "-D
I have a Pull Request to fix the website build waiting for reviews.
https://issues.apache.org/jira/browse/HBASE-25275
On Wed, Nov 11, 2020 at 9:18 PM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:
>
> Build status: FAILURE
>
> The HBase website has not been updated to incorporate
+1 (binding)
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_265): ok
- mvn clean apache-rat:check "-D hadoop.profile=3.0"
* Built from source (1.8.0_265): ok
- mvn clean install -DskipTests "-D hadoop.profile=3.0"
* Unit tests pass (1.8.0_265): ok
- mvn package -P runAllTests "-D
+1
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_265): ok
- mvn clean apache-rat:check
* Built from source (1.8.0_265): ok
- mvn clean install -DskipTests
* Unit tests pass (1.8.0_265): ok
- mvn package -P runAllTests -Dsurefire.rerunFailingTestsCount=3
LTT 1M rows: ok
Thanks Stack! I've managed to update the post.
I have to admit the blog tool is not that user friendly...
Peter
On Fri, Jun 4, 2021 at 5:34 PM Stack wrote:
> On Fri, Jun 4, 2021 at 2:54 AM Peter Somogyi wrote:
>
> > Tried this track now but I was told it is self-serve by the
Congratulations!
On Mon, May 17, 2021 at 8:56 PM Wellington Chevreuil <
wellington.chevre...@gmail.com> wrote:
> Congratulations!
>
> Em seg., 17 de mai. de 2021 às 18:04, Nick Dimiduk
> escreveu:
>
> > Congratulations, Xiaolin, and thank you for all your contributions!!
> >
> > On Sat, May 15,
Hi,
I was asked about an HBase blog post [1] at $dayjob if we could update it
because the images are not available anymore.
Do we have the possibility of updating old posts? I've never created a blog
post in blogs.apache.org so probably I don't have the right permissions.
Luckily, the images can
ticket [1].
>
> Thanks for doing the fix-up.
> S
>
> 1.
>
> https://issues.apache.org/jira/browse/INFRA-4327?jql=project%20%3D%20INFRA%20AND%20text%20~%20%22blog%20account%22
>
> On Thu, Jun 3, 2021 at 6:28 AM Peter Somogyi wrote:
>
> > Hi,
> >
> > I was
Congratulations!
On Mon, Jul 12, 2021 at 12:53 PM Yu Li wrote:
> Congrats and welcome, Baiqiang.
>
> Best Regards,
> Yu
>
>
> On Mon, 12 Jul 2021 at 16:56, 哈晓琳 wrote:
>
> > Congratulations Baiqiang!
> >
> > Balazs Meszaros 于2021年7月12日周一
> > 下午4:35写道：
> >
> > > Congratulations Baiqiang!
> > >
101 - 200 of 855 matches
Mail list logo
