1.0.x series comes compiled with 2.5.1, but it can be run with 2.6.0 without recompiling (I usually do this in release candidate testing). 2.5.1 and 2.6.0 are binary compatible as far as I tested. Although earlier Hadoop versions are not. Thus HDFS-7005 should not have any affect on this RC I think.
HBASE-13471 is pretty critical. I was not involved much in the review. From my reading it will only happen if in a batch there are rows not in the region range. This did not come up in regular testing, and even 0.98 is affected, right? Do you think we should sink this release and do another one? I am trying to do the monthly release train going, in which case, 1.0.2 will contain it if we don't sink it which is hopefully in 4-5 weeks. Enis On Tue, Apr 21, 2015 at 4:28 PM, Elliott Clark <ecl...@apache.org> wrote: > Any thoughts on how HBASE-13471 and HDFS-7005 would affect this RC? > > On Sat, Apr 18, 2015 at 3:17 PM, Ted Yu <yuzhih...@gmail.com> wrote: > > > +1 > > > > Checked signatures > > Ran unit test suite > > Exercised basic shell commands > > > > > > On Fri, Apr 17, 2015 at 11:06 PM, Enis Söztutar <e...@apache.org> wrote: > > > > > I am pleased to announce that the third release candidate for the > release > > > 1.0.1 > > > (HBase-1.0.1RC2), is available for download at > > > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.0.1RC2/ > > > > > > Maven artifacts are also available in the temporary repository > > > https://repository.apache.org/content/repositories/orgapachehbase-1075 > > > > > > Signed with my code signing key E964B5FF. Can be found here: > > > https://people.apache.org/keys/committer/enis.asc > > > > > > Signed tag in the repository can be found here: > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=hbase.git;a=tag;h=e84dbc0b48861b6ff531a82321745f0607a7525f > > > > > > > > > HBase 1.0.1 is the next “patch” release in the 1.0.x release line and > > > supersedes 1.0.0. > > > According to the HBase’s semantic version guide (See [1]), the release > > > candidate is > > > source and binary compatible with 1.0.0 for client applications and > > server > > > side libraries > > > (coprocessors, filters, etc). > > > > > > Binary / source compatibility report with 1.0.0 can be reached here: > > > https://people.apache.org/~enis/1.0.0_1.0.1RC2_compat_report.html > > > > > > > > > 1.0.1 release contains 119 fixes on top of 1.0.0 release. Most of > > > the changes are > > > bug fixes except for the following: > > > > > > [HBASE-13002] - Make encryption cipher configurable > > > [HBASE-13044] - Configuration option for disabling coprocessor loading > > > [HBASE-13054] - Provide more tracing information for locking/latching > > > events. > > > [HBASE-13059] - Set executable bit for scripts in dev-support > > > [HBASE-13086] - Show ZK root node on Master WebUI > > > [HBASE-13109] - Make better SEEK vs SKIP decisions during scanning > > > [HBASE-13120] - Allow disabling hadoop classpath and native library > > lookup > > > [HBASE-13132] - Improve RemoveColumn action debug message > > > [HBASE-13162] - Add capability for cleaning hbase acls to hbase cleanup > > > script. > > > [HBASE-13168] - Backport HBASE-12590 "A solution for data skew in > > > HBase-Mapreduce Job" > > > [HBASE-13183] - Make ZK tickTime configurable in standalone HBase > > > [HBASE-13342] - Fix incorrect interface annotations > > > [HBASE-12869] - Add a REST API implementation of the ClusterManager > > > interface > > > [HBASE-13380] - Cherry pick the HBASE-12808 compatibility checker tool > > back > > > to 0.98+ > > > > > > Full list of the issues can be found at: > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329042&projectId=12310753 > > > < > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329042&projectId=12310753 > > > > > > > > > > Compatibility > > > ------------- > > > This release (1.0.1) is source, wire and binary compatible with 1.0.0 > > > release. Client > > > applications does not have to be recompiled with the new version > (unless > > > new API is used) > > > if upgrading from 1.0.0. It is a drop-in replacement. > > > > > > See release notes for 1.0.0 [2] for compatibility with earlier > > > versions (0.94, 0.96, 0.98). > > > Compatibility of 1.0.1 with earlier versions is the same as in 1.0.0. > > > > > > Source Compatibility: > > > Client side code in HBase-1.0.x is (mostly) source compatible with > 0.98.x > > > versions. Some minor API changes might be needed from the client side. > > > > > > Wire Compatibility: > > > HBase-1.0.x release is wire compatible with 0.98.x releases. Clients > and > > > servers running in different versions as long as new features are not > > used > > > should be possible. > > > A rolling upgrade from 0.98.x clusters to 1.0.x is supported as well. > > > Rolling upgrade from 0.96 directly to 1.0.x is not supported. > > > 1.0.x is NOT wire compatible with earlier releases (0.94, etc). > > > > > > Binary Compatibility: > > > Binary compatibility at the Java API layer with earlier versions > (0.98.x, > > > 0.96.x and 0.94.x) is not supported. You may have to recompile your > > client > > > code and any server side code (coprocessors, filters etc) referring to > > > hbase jars. > > > > > > Other Compatibility issues: > > > - [HBASE-13479] - [branch-1.0] Master should not bind to region server > > > ports > > > (Master now respects hbase.master.port and hbase.master.info.port) > > > - [HBASE-13481] - Master should respect master (old) DNS/bind related > > > configurations > > > - [HBASE-13289 <https://issues.apache.org/jira/browse/HBASE-13289>] - > > > typo > > > in splitSuccessCount metric > > > - [HBASE-13275] - Setting hbase.security.authorization to false does > not > > > disable authorization > > > - [HBASE-13362] - Set max result size from client only (like scanner > > > caching) > > > > > > > > > Upgrading > > > --------- > > > This release is rolling upgradable from 1.0.0 release. > > > > > > See [2] and [3] for upgrade instructions from earlier versions. > Upgrading > > > to 1.0.1 is similar > > > to upgrading to 1.0.0 as documented in [3]. > > > > > > From 0.98.x : Upgrade from 0.98.x in regular upgrade or rolling upgrade > > > fashion > > > is supported. > > > > > > From 0.96.x : Upgrade from 0.96.x is supported with a shutdown and > > restart > > > of > > > the cluster. > > > > > > From 0.94.x : Upgrade from 0.94.x is supported similar to upgrade from > > > 0.94 -> 0.96. The upgrade script should be run to rewrite cluster > level > > > metadata. > > > See [3] for details. > > > > > > > > > Supported Hadoop versions > > > ------------------------- > > > 1.0.x releases support only Hadoop-2.x. Hadoop-2.4.x, Hadoop-2.5.x > > > and Hadoop-2.6.x > > > releases are the most tested hadoop releases and we recommend running > > with > > > those > > > versions (or later versions). Earlier Hadoop-2 based releases > > (hadoop-2.2.x > > > and 2.3.x) > > > are not tested to the full extend. More information can be found at > [4]. > > > > > > > > > Supported Java versions > > > ------------------------- > > > 1.0.x releases only support JDK7. JDK8 support is experimental. More > > > information can be > > > found at [5]. > > > > > > > > > Voting > > > ------ > > > Please try to test and vote on this release by April 24 2015 11:59PM > PDT. > > > > > > [] +1 Release the artifacts as 1.0.1 > > > [] -1 DO NOT release the artifacts as 1.0.1, because... > > > > > > > > > References > > > ---------- > > > [1] https://hbase.apache.org/book/upgrading.html#hbase.versioning > > > [2] http://s.apache.org/hbase-1.0.0-release-notes > > > [3] https://hbase.apache.org/book/upgrade1.0.html#upgrade1.0.changes > > > [4] https://hbase.apache.org/book/configuration.html#hadoop > > > [5] https://hbase.apache.org/book/configuration.html#java > > > > > > Thanks all who worked on this release! > > > Enis > > > > > >
