As we discovered at Salesforce, this breaks mixed 4.1 and 4.2 clients when
those clients use sequences. As soon as the first 4.2 connects to a cluster
upgraded to 4.2 the cluster's metadata is upgraded. At that point 4.1 clients
using sequences are broken.
I propose we sink the RC, remove the upgrade code from 4.2, and push it to 4.3.
That means the sequence table will not be pre-split in 4.2.
Let's discuss, I won't -1 the RC until we do.
Thanks.
-- Lars
From: James Taylor <[email protected]>
To: "[email protected]" <[email protected]>
Sent: Thursday, November 13, 2014 8:25 AM
Subject: [VOTE] Release of Apache Phoenix 4.2.1 RC1
Hello everyone,
This is a call for a vote on Apache Phoenix 4.2.1 RC1. This is a bug
fix/patch release of Phoenix 4.2, compatible with the 0.98 branch of
Apache HBase with feature parity against the Phoenix 3.2 release. The
release includes both a source-only release and a convenience binary
release.
The previous RC was sunk due to a backward compatibility issue and
various other bugs.
For a complete list of changes, see:
https://raw.githubusercontent.com/apache/phoenix/4.2/CHANGES
The source tarball, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.2.1-rc1/src/
The binary artifacts can be found at:
https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.2.1-rc1/bin/
Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/mujtaba.asc
KEYS file available here:
https://dist.apache.org/repos/dist/release/phoenix/KEYS
The hash and tag to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=e00763ee0151518decc2db39b207a6e674c0eebb
https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=tag;h=refs/tags/v4.2.1-rc1
Vote will be open for at least 72 hours. Please vote:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
Thanks,
The Apache Phoenix Team
