[
https://issues.apache.org/jira/browse/HIVE-10982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14988190#comment-14988190
]
Alan Gates commented on HIVE-10982:
-----------------------------------
This patch doesn't apply anymore because of HIVE-11718, which makes some
similar changes. The big difference is it doesn't allow setting fetchSize as
part of the connection properties. If you feel what we have now is good enough
we can close this as a duplicate. Or if you still want to be able to set
fetchSize via the connection properties you can rebase the patch against the
current code.
> Customizable the value of java.sql.statement.setFetchSize in Hive JDBC Driver
> ------------------------------------------------------------------------------
>
> Key: HIVE-10982
> URL: https://issues.apache.org/jira/browse/HIVE-10982
> Project: Hive
> Issue Type: Improvement
> Components: JDBC
> Affects Versions: 1.2.0, 1.2.1
> Reporter: Bing Li
> Assignee: Bing Li
> Priority: Critical
> Attachments: HIVE-10982.1.patch
>
>
> The current JDBC driver for Hive hard-code the value of setFetchSize to 50,
> which will be a bottleneck for performance.
> Pentaho filed this issue as http://jira.pentaho.com/browse/PDI-11511, whose
> status is open.
> Also it has discussion in
> http://forums.pentaho.com/showthread.php?158381-Hive-JDBC-Query-too-slow-too-many-fetches-after-query-execution-Kettle-Xform
> http://mail-archives.apache.org/mod_mbox/hive-user/201307.mbox/%3ccacq46vevgrfqg5rwxnr1psgyz7dcf07mvlo8mm2qit3anm1...@mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
