[
https://issues.apache.org/jira/browse/HIVE-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978321#action_12978321
]
Bennie Schut commented on HIVE-1815:
------------------------------------
Thanks for the comment Edward, fetchN is part of the hive server yes. But the
jdbc driver doesn't use this. The HiveQueryResultSet call's a client.fetchOne();
It would be nice if the jdbc driver uses the fetchN you suggested in the
comment and perhaps keeps a little queue of records and when dropping below a
threshold do another fetchN.
I've also noticed the same slowness and it makes sence this was probably cause
by using fetchOne().
> 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.
