[
https://issues.apache.org/jira/browse/HIVE-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13909361#comment-13909361
]
Hive QA commented on HIVE-5217:
-------------------------------
{color:red}Overall{color}: -1 at least one tests failed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12630053/HIVE-5217.6.patch
{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 5173 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestMinimrCliDriver.testCliDriver_root_dir_external_table
org.apache.hcatalog.hbase.TestHBaseDirectOutputFormat.org.apache.hcatalog.hbase.TestHBaseDirectOutputFormat
{noformat}
Test results:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1439/testReport
Console output:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/1439/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12630053
> Add long polling to asynchronous execution in HiveServer2
> ---------------------------------------------------------
>
> Key: HIVE-5217
> URL: https://issues.apache.org/jira/browse/HIVE-5217
> Project: Hive
> Issue Type: Sub-task
> Components: HiveServer2
> Affects Versions: 0.13.0
> Reporter: Vaibhav Gumashta
> Assignee: Vaibhav Gumashta
> Fix For: 0.13.0
>
> Attachments: HIVE-5217.2.patch, HIVE-5217.3.patch, HIVE-5217.4.patch,
> HIVE-5217.5.patch, HIVE-5217.6.patch, HIVE-5217.D12801.2.patch,
> HIVE-5217.D12801.3.patch, HIVE-5217.D12801.4.patch, HIVE-5217.D12801.5.patch,
> HIVE-5217.D12801.6.patch
>
>
> [HIVE-4617|https://issues.apache.org/jira/browse/HIVE-4617] provides support
> for async execution in HS2. The client gets an operation handle which it can
> poll to check on the operation status. However, the polling frequency is
> entirely left to the client which can be resource inefficient. Long polling
> will solve this, by blocking the client request to check the operation status
> for a configurable amount of time (a new HS2 config) if the data is not
> available, but responding immediately if the data is available.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
