hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (Jira)" <>
Subject [jira] [Commented] (HIVE-22853) Allow JDBC FetchSize to Be Set in Beeline
Date Thu, 12 Mar 2020 15:11:00 GMT


Hive QA commented on HIVE-22853:

Here are the results of testing the latest attachment:

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

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

Test results:
Console output:
Test logs:

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

This message is automatically generated.

ATTACHMENT ID: 12996426 - PreCommit-HIVE-Build

> Allow JDBC FetchSize to Be Set in Beeline
> -----------------------------------------
>                 Key: HIVE-22853
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Beeline
>    Affects Versions: 4.0.0
>            Reporter: Naveen Gangam
>            Assignee: David Mollitor
>            Priority: Major
>         Attachments: HIVE-22853.2.patch, HIVE-22853.3.patch, HIVE-22853.4.patch, HIVE-22853.5.patch,
HIVE-22853.6.patch, HIVE-22853.7.patch, HIVE-22853.patch
> Currently beeline uses a hard coded default of 1000 rows for fetchSize. This default
value is different from what the server has set. While the beeline user can reset the value
via set command, its cumbersome to change the workloads.
> Rather it should default to the server-side value and set should be used to override
within the session.

This message was sent by Atlassian Jira

View raw message