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

Hive QA commented on HIVE-19096:
--------------------------------



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

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

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

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL 
https://issues.apache.org/jira/secure/attachment/12925860/HIVE-19096.3.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: 12925860 - PreCommit-HIVE-Build

> query result cache interferes with explain analyze 
> ---------------------------------------------------
>
>                 Key: HIVE-19096
>                 URL: https://issues.apache.org/jira/browse/HIVE-19096
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Zoltan Haindrich
>            Assignee: Jason Dere
>            Priority: Major
>         Attachments: HIVE-19096.1.patch, HIVE-19096.2.patch, 
> HIVE-19096.3.patch
>
>
> if  result cache is active; the explain analyze doesn't really return usefull 
> informations; even for unseen queries the result is like this:
> {code}
> +----------------------------------------+
> |                Explain                 |
> +----------------------------------------+
> | Stage-0                                |
> |   Fetch Operator                       |
> |     Cached Query Result:true,limit:-1  |
> |                                        |
> +----------------------------------------+
> {code}



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

Reply via email to