HBase 0.94.12 (+Hadoop 1.0.4)
What version of HBase are you on?On Sun, Apr 6, 2014 at 1:22 PM, Amit Sela <email@example.com> wrote:
The explain result is:CLIENT PARALLEL 23-WAY SKIP SCAN ON 31 KEYS OVER ADSERVER.INVENTORY_SNAPPY ['20140101_US____'] - ['20140131_US____']
Thanks,Amit.On Sun, Apr 6, 2014 at 7:16 PM, James Taylor <firstname.lastname@example.org> wrote:
Hi Amit,Would it be possible to post your CREATE TABLE statement, the EXPLAIN on the query, and the query itself so we can better diagnose any issues?From your description above, you're executing the right query - it's always better to query for multiple rows versus executing a single query for each row (this is typically the case for any query engine).Batching is implemented in 2.2.3 and above, but not for performance reasons. Some products for which we have integration rely on a JDBC driver to support batching, so that's why it was added. Batching does not buy you anything in Phoenix, because it's an embedded JDBC driver.Thanks,JamesOn Sun, Apr 6, 2014 at 9:08 AM, Amit Sela <email@example.com> wrote:
Hi all,I'm running with Phoenix 2.2.2 which (AFAIK) does not support batch queries.I want to query some (not all) of the columns in the table (all from the same family), for multiple rowkeys.
Normally I would execute a batch queries of:select c1,c2... from table where rowkey=row1select c1,c2... from table where rowkey=row2...Since batch is not supported, I do the following:select c1,c2... from table where rowkey in (row1,row2...)This ends up being slower than executing a batch of gets from the HBase API...Is there a better way for me to use Phoenix in this case ?Thanks,Amit.