[
https://issues.apache.org/jira/browse/PHOENIX-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14197314#comment-14197314
]
James Taylor commented on PHOENIX-1404:
---------------------------------------
I'm not sure how we'd be able to support this, as our queries kick off scans
that run in parallel, each scan pulling phoenix.query.scanResultChunkSize rows.
Setting this on the ResultSet would be too late and have no effect. We could
potentially just ignore the ResultSet.setFetchSize() call, or we could have
ChunkedResultIterator use the ResultSet.getFetchSize() for the next set of
calls.
Thoughts, [~gabriel.reid]?
> PhoenixResultSet.setFetchSize throws SQLFeatureNotSupportedException
> --------------------------------------------------------------------
>
> Key: PHOENIX-1404
> URL: https://issues.apache.org/jira/browse/PHOENIX-1404
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0
> Reporter: Josh Mahonin
>
> I've run into this issue when attempting to use Phoenix with both R Studio
> (with RJDBC), as well as ElasticSearch
> Lots of libraries attempt a setFetchSize() on a JDBC result set, but very few
> of them have error handling code, unfortunately. Rather than attempting to
> patch each library, it would be nice if Phoenix could handle this call.
> Is it as simple as invoking "statement.setFetchSize()" in this method?
> https://github.com/apache/phoenix/blob/4ed9ddb8fd28dffcd686671c18dc89d12b0a1c0c/phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixResultSet.java#L784
> I suspect not, but if someone can take a quick look I can make the necessary
> code change and submit a patch.
> Related to PHOENIX-1175
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
