hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-20621) GetOperationStatus called in resultset.next causing incremental slowness
Date Sun, 23 Sep 2018 08:00:02 GMT

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

Hive QA commented on HIVE-20621:
--------------------------------



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

{color:red}ERROR:{color} -1 due to build exiting with an error

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

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL https://issues.apache.org/jira/secure/attachment/12940874/HIVE-20621.2.patch
was found in seen patch url's cache and a test was probably run already on it. Aborting...
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12940874 - PreCommit-HIVE-Build

> GetOperationStatus called in resultset.next causing incremental slowness
> ------------------------------------------------------------------------
>
>                 Key: HIVE-20621
>                 URL: https://issues.apache.org/jira/browse/HIVE-20621
>             Project: Hive
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 4.0.0, 3.2.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>            Priority: Major
>         Attachments: HIVE-20621.1.patch, HIVE-20621.2.patch
>
>
> Fetching result set for a result cache hit query gets slower as more rows are fetched.
For fetching 10 row result set it took about 900ms but fetching 200 row result set took 8
seconds. 
> Reason for this slowness is GetOperationStatus is invoked inside resultset.next() and
it happens for every row even after operation has completed. This is one RPC call per row
fetched (there is also connection overhead without keepalive). 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message