phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vijay Kukkala <>
Subject Re: Scan performance using JDBC result impacted by limit
Date Wed, 21 Jan 2015 17:04:59 GMT
Just to add more info on issue we were facing and workaround applied
the PhoenixResultSet.getString() takes way much time than

the Formatting and other logic in the getString() increases with the number
of items to be processed.

Somebody might want to take a look at this.

On Fri Jan 16 2015 at 3:03:18 PM Vijay Kukkala <>

> I am using plain JDBC code to execute a query against a Phoenix cluster
> running 4.0.0 with Hbase 0.98.x
> My query is as follows against a table with single column_family.
> select cid,ts,id,pc,un,ug,ui,s,inf,sm,mst,se  from wcs_re where cid = ?
> and ts >= ? and ts <= ? limit ?
> <cid, ts, id> are my primary keys for the table.
> On the client side, the retrieved values are Iterated and converted to a
> domain object on the client side. Since the query was taking long, I
> started measuring the times taken to do the conversion for each object.
> The issue I see is, as I increase the limit clause value in the query from
> 100, 1000, 2000 and so on, my domain conversion time increases gradually
> from <1 , 9, 17 ms for each record retrieved from the resultset. Ideally, I
> would have thought that conversion time would be constant.
> Can somebody help shed some light on this?
> thanks
> Vijay

View raw message