hive-dev 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-5519) Use paging mechanism for templeton get requests.
Date Sat, 26 Oct 2013 20:04:30 GMT

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

Hive QA commented on HIVE-5519:
-------------------------------



{color:green}Overall{color}: +1 all checks pass

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

{color:green}SUCCESS:{color} +1 4483 tests passed

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/1251/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/1251/console

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

> Use paging mechanism for templeton get requests.
> ------------------------------------------------
>
>                 Key: HIVE-5519
>                 URL: https://issues.apache.org/jira/browse/HIVE-5519
>             Project: Hive
>          Issue Type: Bug
>          Components: WebHCat
>            Reporter: Hari Sankar Sivarama Subramaniyan
>            Assignee: Hari Sankar Sivarama Subramaniyan
>         Attachments: HIVE-5519.1.patch.txt, HIVE-5519.2.patch.txt
>
>
> Issuing a command to retrieve the jobs field using
> "https://mwinkledemo.azurehdinsight.net:563/templeton/v1/queue/<job_id>?user.name=admin&fields=*"
--user u:p
> will result in timeout in windows machine. The issue happens because of the amount of
data that needs to be fetched. The proposal is to use paging based encoding scheme so that
we flush the contents regularly and the client does not time out.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message