+1

Checked NOTICE and LICENSE files for both binary and source releases
Built from scratch and ran all unit tests successfully
Successfully migrated 2.2.0 tables to 3.0.0
Successfully ran performance script over 10M rows


On Fri, Mar 28, 2014 at 1:54 PM, James Taylor <jamestay...@apache.org>wrote:

> Hi everyone,
> This is a call for a vote on Apache Phoenix 3.0.0 incubating RC3. This is
> the next major release of Phoenix compatible with the 0.94 branch of Apache
> HBase and will be our second release in the incubator. The previous RC was
> sunk due to some errors in the NOTICE and LICENSE files and a potential
> connection leak bug. This new RC fixes these issues. The release includes
> both a source-only release and a convenience binary release.
>
> New features include:
> - Equi-joins through broadcast hash join
> - Shared tables over same physical HBase table
> - Read-only and updatable views
> - Multi-tenancy
> - JDBC ARRAY type
> - Sequence creation and usage
>
> The source tarball, including signatures, digests, etc can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-3.0.0-incubating-rc3/src/
>
> The binary artifacts can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-3.0.0-incubating-rc3/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/incubator/phoenix/KEYS
>
> The hash and tag to be voted on:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=commit;h=363e71bfd7cf6576657dddb484c6a48de9b8de61
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=tag;h=refs/tags/v3.0.0-incubating-rc3
>
> For information about the contents of this release see:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=log;h=refs/tags/v3.0.0-incubating-rc3
>
> 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
>

Reply via email to