One thing I would like to suggest is a change to the project compatibility
policy for upgrade/downgrade to support the following:
Mixed client/server versions one minor release up or back. Going forward. So in
the future eg client={ 4.14, 4.15, 4.16 } <-> server={ 4.14, 4.15, 4.16 }. This
will allow for seamless rolling upgrades with rollback in all common scenarios.
Then, consider an exception for some combinations of 4.15 and 5.1? I have
tested this and these versions are data compatible (create data with 1.5/4.14,
upgrade to 2.2/5.1) and at the HBase level the wire compatibility between 1 and
2 is good enough for normal client operations. If the version check didn’t
throw an exception I wonder if there would be any issue.
For your consideration.
> On Dec 21, 2019, at 2:40 AM, "[email protected]" <[email protected]> wrote:
>
> Yeah! Finally.
> Let's use this time to stabilize; especially the metadata management and
> upgrade testing (and perhaps the HBase compatibility), so that we can have a
> smooth 4.16.0 release.
>
> On Saturday, December 21, 2019, 1:19:34 AM GMT+1, Chinmay Kulkarni
> <[email protected]> wrote:
>
> Hello Everyone,
>
> The Apache Phoenix team is pleased to announce the immediate availability
> of the 4.15.0 minor release. Apache Phoenix enables SQL-based OLTP and
> operational analytics for Apache Hadoop using Apache HBase as its backing
> store and providing integration with other projects in the Apache ecosystem
> such as Spark, Hive, Pig, Flume, and MapReduce.
>
> This minor release has feature parity with supported HBase versions and
> includes the following improvements:
> - Support for multi-region SYSTEM.CATALOG
> - Omid integration with Phoenix
> - Orphan view tool
> - Separation of the Phoenix-Connectors and Phoenix-Queryserver projects
> - 150+ bug fixes
> and much more
>
> Download source and binaries here [1].
>
> Thanks,
> Chinmay Kulkarni
> (on behalf of the Apache Phoenix team)
>
> [1] http://phoenix.apache.org/download.html
>
> --
> Chinmay Kulkarni
