+1(binding)
Checked sigs and sums: Matched
Rat check: Passed
Built from src: OK
Stack 于2019年6月12日周三 上午4:15写道：
> On Tue, Jun 11, 2019 at 2:54 AM Guanghao Zhang wrote:
>
> > RC6 is almost same with RC5. So we can carry the RC5's three binding +1
> and
> > one non-binding +1 here? And one more
Duo Zhang created HBASE-22569:
-
Summary: Should treat null consistency as Consistency.STRONG in
ConnectionUtils.timelineConsistentRead
Key: HBASE-22569
URL: https://issues.apache.org/jira/browse/HBASE-22569
On Tue, Jun 11, 2019 at 2:54 AM Guanghao Zhang wrote:
> RC6 is almost same with RC5. So we can carry the RC5's three binding +1 and
> one non-binding +1 here? And one more +1 from me.
>
No vote carrying Guanghao. If same as RC5, shouldn't take long to gather up
the votes again.
+1 from me on
Josh Elser created HBASE-22568:
--
Summary: [2.1] Upgrade to Jetty 9.3.latest and Jackson 2.9.latest
Key: HBASE-22568
URL: https://issues.apache.org/jira/browse/HBASE-22568
Project: HBase
Issue
Wellington Chevreuil created HBASE-22567:
Summary: HBCK2 addMissingRegionsToMeta
Key: HBASE-22567
URL: https://issues.apache.org/jira/browse/HBASE-22567
Project: HBase
Issue Type:
> have the foot of CHANGES and RELEASENOTES point to hosted, next older
RELEASENOTES/CHANGES hosted in our release dir
+1
On Mon, Jun 10, 2019 at 10:05 PM Stack wrote:
> HBASE-21935 tries to automate the generation of RELEASENOTES.md and
> CHANGES.md. It has yetus interpolates those that made
Josh Elser created HBASE-22566:
--
Summary: Call out default compaction and flush throttling for 2.x
in Book
Key: HBASE-22566
URL: https://issues.apache.org/jira/browse/HBASE-22566
Project: HBase
Murtaza Hassan created HBASE-22565:
--
Summary: Javadoc Warnings: @see cannot be used in inline
documentation
Key: HBASE-22565
URL: https://issues.apache.org/jira/browse/HBASE-22565
Project: HBase
After three binding +1s, plus two non-binding +1s and no 0 or -1 votes,
this "vote" has passed!
Thank you to all who voted on this first alpha release candidate for
hbase-filesystem!
Em seg, 10 de jun de 2019 às 20:17, Esteban Gutierrez
escreveu:
> +1
>
> - Build from source: OK
> - Tests
OK...
Guanghao Zhang 于2019年6月11日周二 下午6:07写道：
> >
> > Better adding a note at the bottom of CHANGES.md and RELEASENOTES.md to
> > mention that all the changes in 2.1.0 are also included in 2.2.0, as
> > discussed in another thread?
> >
> We didn't reached a conclusion yet in the DISCUSS thread?
>
> Better adding a note at the bottom of CHANGES.md and RELEASENOTES.md to
> mention that all the changes in 2.1.0 are also included in 2.2.0, as
> discussed in another thread?
>
We didn't reached a conclusion yet in the DISCUSS thread? 2.2.0 has been
delayed too long to release. I thought we can
RC6 is almost same with RC5. So we can carry the RC5's three binding +1 and
one non-binding +1 here? And one more +1 from me.
Better adding a note at the bottom of CHANGES.md and RELEASENOTES.md to
mention that all the changes in 2.1.0 are also included in 2.2.0, as
discussed in another thread?
Guanghao Zhang 于2019年6月11日周二 下午5:48写道：
> Please vote on this release candidate (RC) for Apache HBase 2.2.0.
> This is the
Filed https://issues.apache.org/jira/browse/HBASE-22564
张铎(Duo Zhang) 于2019年6月11日周二 下午3:53写道：
> Let me do a YCSB test about the performance.
>
> Stack 于2019年6月11日周二 下午1:15写道：
>
>> +1 on merge from me.
>>
>> It removes the complicated multi-threaded edifice we'd built client-side
>> to
>> fake
Please vote on this release candidate (RC) for Apache HBase 2.2.0.
This is the first release of the branch-2.2 line.
RC6 is almost same with RC5. The biggest change is the release note, which
added the release note of HBASE-21970 about how to upgrade 2.0 or 2.1
cluster to 2.2+. So this VOTE will
Duo Zhang created HBASE-22564:
-
Summary: Compare performance number with old sync client
implementation
Key: HBASE-22564
URL: https://issues.apache.org/jira/browse/HBASE-22564
Project: HBase
Let me do a YCSB test about the performance.
Stack 于2019年6月11日周二 下午1:15写道：
> +1 on merge from me.
>
> It removes the complicated multi-threaded edifice we'd built client-side to
> fake an async behavior replacing it with an actual async implementation.
> Users will immediately notice a radical
Thanks Josh for acting on this!
On Tue, Jun 11, 2019 at 3:15 AM Sean Busbey wrote:
> We used to have a build step that compressed our logs for us. I don't think
> Jenkins can read the test results if we do the xml files from surefire, so
> I'm not sure how much space we can save. That's where
18 matches
Mail list logo
