The getFetchSize() is already based on the hbase.client.scanner.caching setting, so there's not a big need. The only advantage would be if per statement you wanted different caching. Is that the case for you?
Thanks, James On Mon, Mar 10, 2014 at 10:11 AM, alex kamil <[email protected]> wrote: > are there any plans to implement setFetchSize in PhoenixStatement? > > when retrieving large number of rows the resultSet generates lots of > network calls back to Hbase > > > phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixStatement.java: > > @Override > > public void setFetchSize(int rows) throws SQLException { > > // TODO: map to Scan.setBatch() ? > > throw new SQLFeatureNotSupportedException(); > > } >
