[
https://issues.apache.org/jira/browse/HIVE-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978476#action_12978476
]
Steven Wong commented on HIVE-1815:
-----------------------------------
Using fetchN will be nice. The Hive driver should use fetchN in accordance with
the fetch size setting in the Statement or ResultSet object as set by
setFetchSize, which will need to be implemented along with using fetchN. (The
Hive driver currently does not support setFetchSize and getFetchSize.)
> The class HiveResultSet should implement batch fetching.
> --------------------------------------------------------
>
> Key: HIVE-1815
> URL: https://issues.apache.org/jira/browse/HIVE-1815
> Project: Hive
> Issue Type: Improvement
> Components: JDBC
> Affects Versions: 0.5.0
> Environment: Custom Java application using the Hive JDBC driver to
> connect to a Hive server, execute a Hive query and process the results.
> Reporter: Guy le Mar
> Fix For: 0.6.0
>
>
> When using the Hive JDBC driver, you can execute a Hive query and obtain a
> HiveResultSet instance that contains the results of the query.
> Unfortunately, HiveResultSet can then only fetch a single row of these
> results from the Hive server at a time. As a consequence, it's extremely slow
> to fetch a resultset of anything other than a trivial size.
> It would be nice for the HiveResultSet to be able to fetch N rows from the
> server at a time, so that performance is suitable to support applications
> that provide human interaction.
> (From memory, I think it took me around 20 minutes to fetch 4000 rows.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
