Re: ResultSet size

So HBase (and by extension, Phoenix) does not do true "streaming" of rows - rows are copied into memory from the HFiles and then eventually copied en-mass onto the wire. On the client they are pulled off in chunks and paged through by the client scanner. You can control the batch size (amount of

Re: ResultSet size

To add to what Jesse said, you can override the default scanner fetch size programmatically via Phoenix by calling statement.setFetchSize(int). On Tuesday, October 6, 2015, Jesse Yates wrote: > So HBase (and by extension, Phoenix) does not do true "streaming" of rows > -

Re: ResultSet size

.com> > *To:* "user@phoenix.apache.org" <user@phoenix.apache.org> > *Cc:* Sumit Nigam <sumit_o...@yahoo.com> > *Sent:* Tuesday, October 6, 2015 9:20 PM > *Subject:* Re: ResultSet size > > To add to what Jesse said, you can override the default scanner fetch

Re: ResultSet size

<samarth.j...@gmail.com> To: "user@phoenix.apache.org" <user@phoenix.apache.org> Cc: Sumit Nigam <sumit_o...@yahoo.com> Sent: Tuesday, October 6, 2015 9:20 PM Subject: Re: ResultSet size To add to what Jesse said, you can override the default scanner fetch size