phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Taylor <>
Subject Re: performance on created table on existing hbase table
Date Tue, 18 Mar 2014 17:04:56 GMT
Hi Weiping,
Take a look at our FAQ here[1] and in particular, this question "How I
create Views in Phoenix? What's the difference between Views/Tables?". You
can map to existing HBase tables, depending on how you formed your row key
and how you serialized you key value data.

We also support bulk loading of CSV files through either our bin/
script or through map-reduce.

Typically, in HBase, you design your table with a composite row key. This
is supported in Phoenix by defining a primary key constraint with more than
one column. If you describe your use case here, we can give you advice on
the most optimal schema. Since it sounds like you're in the evaluation
phase, I'd recommend creating a new table and trying our bin/
script. In that way, you'll get some feel for importing data as well as
querying it.



On Tue, Mar 18, 2014 at 9:36 AM, Weiping Qu <> wrote:

> Hello,
> I am new to phoenix.
> Before getting touch with Phoenix, I used my own customized MapReduce jobs
> to Bulk load my hbase table (using HFileOutpuFormat), and I found in the
> web that the scan performance can be improved by using phoenix, especially
> LIMIT clause is supported by Phoenix query optimizer.
> So I'd like to try Phoenix for my test.
> But how can I use phoenix to query my existing table. Do I have to create
> table on that?
> Or I have to create a phoenix table, then the question turns to whether I
> still can use my own MapReduce jobs to populate the phoenix table.
> In which case, the performance is better?
> Kindly help me out
> Thanks
> Weiping

View raw message