+1 on the 4.2.1 RC1. I¹ve downloaded the bin tar-ball & setup on 0.98.4-hadoop2. All following steps run smoothly.
1) Use sqlline create & drop a table 2) use psql creates a table, load data & query data 3) run ./bin/performance.py localhost 100000 On 11/13/14, 9:25 AM, "James Taylor" <[email protected]> wrote: >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=e00763ee0 >151518decc2db39b207a6e674c0eebb >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 -- 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.
