[ 
https://issues.apache.org/jira/browse/HIVE-23007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067488#comment-17067488
 ] 

Hive QA commented on HIVE-23007:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12997764/HIVE-23017.3.patch

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 18135 tests passed

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/21275/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/21275/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-21275/

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: 12997764 - PreCommit-HIVE-Build

> Do Not Consider Client Session For Default Fetch Size
> -----------------------------------------------------
>
>                 Key: HIVE-23007
>                 URL: https://issues.apache.org/jira/browse/HIVE-23007
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: David Mollitor
>            Assignee: David Mollitor
>            Priority: Major
>         Attachments: HIVE-23007.1.patch, HIVE-23007.2.patch, 
> HIVE-23017.3.patch, HIVE-23017.3.patch
>
>
> Right now, when a client makes a new session, it's value override's the 
> server's value for {{hive.server2.thrift.resultset.default.fetch.size}}.  
> This is a server-side configuration and the client should not dictate what 
> the server's default (preferred) size is.
> * Remove superfluous null check
> * Use a Collection's Singleton Map instead of creating a full-sized HashMap
> * Code simplification



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to