t;
> *Cc:* Sumit Nigam
> *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
> programmatically via Phoenix by calling statement.setFetchSize(int).
> On Tuesday, October 6, 2015,
Jain
To: "user@phoenix.apache.org"
Cc: Sumit Nigam
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
programmatically via Phoenix by calling statement.setFetchSize(int).
On Tuesday, Oc
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
> - rows are copied into memo
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 ro
Hi,
Does Phoenix buffer the result set internally? I mean when I fire a huge skip
scan IN clause, then the data being returned may be too huge to contain in
memory. So, ideally I'd like to stream data through the resultset.next()
method. So, my question is does Phoenix really stream results?
An
