Vijay, Is there a reason why you are doing PhoenixResultSet.string()? Is it for logging purposes?
Regarding your question regarding increase in object creation time, that doesn't seem like it is phoenix related. Are you seeing an increase in time for resultset.next() or are you seeing an increase in time for resultset.getObject()? -Samarth On Wednesday, January 21, 2015, Vijay Kukkala <[email protected]> wrote: > Just to add more info on issue we were facing and workaround applied > the PhoenixResultSet.getString() takes way much time than > PhoenixResultSet.getBytes(). > > 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 <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > >> 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 >> >
