+1

Verified checksums
Ran full build
Ran tests


On Mon, Mar 24, 2014 at 2:05 PM, Simon Töns <[email protected]> wrote:

> +1
>
> Simon
>
> > On Mar 24, 2014, at 10:05, Mujtaba Chohan <[email protected]> wrote:
> >
> > +1.
> >
> > * Artifacts builds fine for both Hadoop-1, 2 profiles.
> > * Performance is better or on par. for most queries compared to last
> > release
> >
> http://phoenix-bin.github.io/client/performance/phoenix-20140324122633.htm
> >
> >
> > On Mon, Mar 24, 2014 at 12:42 PM, James Taylor <[email protected]
> >wrote:
> >
> >> I don't think the missing examples are a big enough issue to warrant a
> new
> >> RC. We can always provide a separate download for the couple of .sql and
> >> .csv files we have in the examples directory.
> >>
> >> Thanks,
> >> James
> >>
> >>
> >> On Mon, Mar 24, 2014 at 12:17 PM, Mujtaba Chohan <[email protected]>
> >> wrote:
> >>
> >>> Jeffrey - phoenix-core-4.0.0-incubating.jar was named as
> >>> phoenix-4.0.0-incubating.jar to match naming convention of previous
> >>> releases.
> >>>
> >>> Yes. 4.0.0 tar is missing examples. Can I add missing examples without
> >>> starting a new RC?
> >>>
> >>> Thanks,
> >>> Mujtaba
> >>>
> >>>
> >>> On Mon, Mar 24, 2014 at 12:12 PM, Jeffrey Zhong <
> [email protected]
> >>>> wrote:
> >>>
> >>>>
> >>>> I downloaded the tar ball phoenix-4.0.0-incubating.tar.gz and found it
> >>>> doesn't contain phoenix-core-4.0.0-incubating.jar & example files.
> >>>>
> >>>> Thanks
> >>>> -Jeffrey
> >>>>
> >>>>> On 3/21/14 3:49 PM, "James Taylor" <[email protected]> wrote:
> >>>>>
> >>>>> Hi everyone,
> >>>>> This is a call for a vote on Apache Phoenix 4.0.0 incubating RC1.
> >> Thanks
> >>>>> for the feedback on the previous RC. This is the next major release
> of
> >>>>> Phoenix compatible with the 0.98 branch of Apache HBase (0.98.1+) and
> >>> will
> >>>>> be our third release in the incubator. The release includes both a
> >>>>> source-only release and a convenience binary release.
> >>>>>
> >>>>> The 4.0.0 release has feature parity with our pending 3.0.0 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-4.0.0-inc
> >>>>> ubating-rc1/src/
> >>>>>
> >>>>> The binary artifacts can be found at:
> >>
> https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-4.0.0-inc
> >>>>> ubating-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/dev/incubator/phoenix/KEYS
> >>>>>
> >>>>> The tag to be voted upon:
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=tag;h=re
> >>>>> fs/tags/v4.0.0-incubating-rc1
> >>>>>
> >>>>> For information about the contents of this release see:
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=log;h=re
> >>>>> fs/tags/v4.0.0-incubating-rc1
> >>>>>
> >>>>> Release notes
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12326145&st
> >>>
> >>>
> yleName=Text&projectId=12315120&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDE
> >>>>> D%7C34a706e780c7e8f198c9ca903e80572b560599b6%7Clin
> >>>>>
> >>>>> Vote will be open for at least 72 hours. Please vote:
> >>>>>
> >>>>> [ ] +1 approve
> >>>>> [ ] +0 no opinion
> >>>>> [ ] -1 disapprove (and reason why)
> >>>>>
> >>>>> Thanks,
> >>>>> James
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> CONFIDENTIALITY NOTICE
> >>>> NOTICE: This message is intended for the use of the individual or
> >> entity
> >>> to
> >>>> which it is addressed and may contain information that is
> confidential,
> >>>> privileged and exempt from disclosure under applicable law. If the
> >> reader
> >>>> of this message is not the intended recipient, you are hereby notified
> >>> that
> >>>> any printing, copying, dissemination, distribution, disclosure or
> >>>> forwarding of this communication is strictly prohibited. If you have
> >>>> received this communication in error, please contact the sender
> >>> immediately
> >>>> and delete it from your system. Thank You.
> >>
>

Reply via email to