[
https://issues.apache.org/jira/browse/HIVE-23096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069932#comment-17069932
]
Hive QA commented on HIVE-23096:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12998040/HIVE-23096.1.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 18140 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/21314/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/21314/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-21314/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12998040 - PreCommit-HIVE-Build
> Detect Small Fetch Size on HS2
> ------------------------------
>
> Key: HIVE-23096
> URL: https://issues.apache.org/jira/browse/HIVE-23096
> Project: Hive
> Issue Type: Sub-task
> Reporter: David Mollitor
> Assignee: David Mollitor
> Priority: Minor
> Attachments: HIVE-23096.1.patch
>
>
> See if there's an easy and useful way of detecting when user's are using a
> small fetch size inadvertently. For example, a JDBC fetchSize of 1, for a
> result set of 1,000,000 rows across a high-latency link may crush performance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
