Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates
 209.85.220.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAG_TOPCs-DmSfKPVAKdMfCHfa=mkaye2gsgcwor_V93dJNa58g@mail.gmail.com>
References: 
 <CAG_TOPCs-DmSfKPVAKdMfCHfa=mkaye2gsgcwor_V93dJNa58g@mail.gmail.com>
Date: Thu, 24 Oct 2013 17:40:22 -0700
Message-ID: 
 <CALte62wvUGCh_ZQsGyQ3HizD+KXM5stLtU7-wBRp=fSEvi0-2Q@mail.gmail.com>
Subject: Re: [ANNOUNCE] Phoenix v 2.1 released
From: Ted Yu <yuzhihong@gmail.com>
To: "user@hbase.apache.org" <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a11362c2ed5d2bb04e985fe2a

--001a11362c2ed5d2bb04e985fe2a
Content-Type: text/plain; charset=ISO-8859-1

>From https://github.com/forcedotcom/phoenix/wiki/Secondary-Indexing :
Is date_col a column from data table ?

CREATE INDEX my_index ON my_table (date_col DESC, v1) INCLUDE (v3)
    SALT_BUCKETS=10, DATA_BLOCK_ENCODING='NONE';


On Thu, Oct 24, 2013 at 5:24 PM, James Taylor <jtaylor@salesforce.com>wrote:

> The Phoenix team is pleased to announce the immediate availability of
> Phoenix 2.1 [1].
> More than 20 individuals contributed to the release. Here are some of the
> new features
> now available:
> * Secondary Indexing [2] to create and automatically maintain global
> indexes over your
>    primary table.
>    - Queries automatically use an index when more efficient, turning your
> full table scans
>      into point and range scans.
>    - Multiple columns may be indexed in ascending or descending sort order.
>    - Additional primary table columns may be included in the index to form
> a covered
>      index.
>    - Available in two flavors:
>         o Server-side index maintenance for mutable data.
>         o Client-side index maintenance optimized for write-once,
> append-only use cases.
> * Row Value Constructors [3], a standard SQL construct to efficiently
> locate the row at
>   or after a composite key value.
>    - Enables a query-more capability to efficiently step through your data.
>    - Optimizes IN list of composite key values to be point gets.
> * Map-reduce based CSV Bulk Loader [4] to build Phoenix-compliant HFiles
> and load
>   them into HBase.
> * MD5 hash and INVERT built-in functions
>
> Phoenix 2.1 requires HBase 0.94.4 or above, with 0.94.10 or above required
> for mutable secondary indexing. For the best performance, we recommend
> HBase 0.94.12 or above.
>
> Regards,
>
> James
> @JamesPlusPlus
> http://phoenix-hbase.blogspot.com/
>
> [1] https://github.com/forcedotcom/phoenix/wiki/Download
> [2] https://github.com/forcedotcom/phoenix/wiki/Secondary-Indexing
> [3] https://github.com/forcedotcom/phoenix/wiki/Row-Value-Constructors
> [4]
>
> https://github.com/forcedotcom/phoenix/wiki/Bulk-CSV-loading-through-map-reduce
>

--001a11362c2ed5d2bb04e985fe2a--