+1 (binding)
Here's what I did:
- built from source- inspected the bin tar-ball- loaded some data, scanned, 
deleted, etc- did the same using upcoming Phoenix 4.15.0- nothing undue in the 
logs
-- Lars
    On Tuesday, October 8, 2019, 07:08:07 PM PDT, Andrew Purtell 
<[email protected]> wrote:  
 
 The fifth HBase 1.5.0 release candidate (RC4) is available for download at
https://dist.apache.org/repos/dist/dev/hbase/1.5.0RC4/ and Maven artifacts
are available in the temporary repository
https://repository.apache.org/content/repositories/orgapachehbase-1364/ .

The git tag corresponding to the candidate is '1.5.0RC4’ (d14e335edc).

A detailed source and binary compatibility report for this release is
available for your review at
https://dist.apache.org/repos/dist/dev/hbase/1.5.0RC4/compat-check-report.html
. I believe the reported changes conform to the compatibility guidelines
for a minor release. Method additions to Public and LimitedPrivate
interfaces are allowed. A method has been removed from a
LimitedPrivate(Config) interface but should have no practical impact.

A list of the 203 issues resolved in this release can be found at
https://s.apache.org/h3y00 . The 1.5.0 changelog is derived from the
changelog of the last branch-1.4 release, 1.4.10.

Please try out the candidate and vote +1/0/-1.

The vote will be open for at least 72 hours. Unless objection I will try to
close it Monday October 14, 2019 if we have sufficient votes.

Prior to making this announcement I made the following preflight checks:

    RAT check passes (7u80)
    Unit test suite passes (7u80, 8u222)*
    Opened the UI in a browser, poked around, used the profiler servlet a
few times to look at flamegraph and tree output.
    LTT load 10M rows with 100% verification and 20% updates (8u212)
    ITBLL 100M rows with slowDeterministic monkey (8u222)

* - There are known flaky tests. If you would like, you can download a list
of exclude patterns from
https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-1/
.

--
Best regards,
Andrew  

Reply via email to