[
https://issues.apache.org/jira/browse/HIVE-20834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674049#comment-16674049
]
Hive QA commented on HIVE-20834:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12946700/HIVE-20834.3.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 15520 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/14722/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/14722/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-14722/
Messages:
{noformat}
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
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12946700 - PreCommit-HIVE-Build
> Hive QueryResultCache entries keeping reference to SemanticAnalyzer from
> cached query
> -------------------------------------------------------------------------------------
>
> Key: HIVE-20834
> URL: https://issues.apache.org/jira/browse/HIVE-20834
> Project: Hive
> Issue Type: Bug
> Reporter: Jason Dere
> Assignee: Jason Dere
> Priority: Major
> Attachments: HIVE-20834.1.patch, HIVE-20834.2.patch,
> HIVE-20834.3.patch, dominator_tree.png
>
>
> QueryResultCache.LookupInfo ends up keeping a reference to the
> SemanticAnalyzer from the cached query, for as long as the cached entry is in
> the cache. We should not be keeping the SemanticAnalyzer around after the
> query is done executing since they can hold on to quite a bit of memory.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
