[jira] [Updated] (HIVE-20834) Hive QueryResultCache entries keeping reference to SemanticAnalyzer from cached query

2018-11-03 Thread Jason Dere (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-20834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dere updated HIVE-20834:
--
   Resolution: Fixed
Fix Version/s: 4.0.0
   Status: Resolved  (was: Patch Available)

I've committed this to master

> 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
> Fix For: 4.0.0
>
> 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)


[jira] [Updated] (HIVE-20834) Hive QueryResultCache entries keeping reference to SemanticAnalyzer from cached query

2018-11-02 Thread Jason Dere (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-20834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dere updated HIVE-20834:
--
Attachment: HIVE-20834.3.patch

> 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)


[jira] [Updated] (HIVE-20834) Hive QueryResultCache entries keeping reference to SemanticAnalyzer from cached query

2018-11-01 Thread Jason Dere (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-20834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dere updated HIVE-20834:
--
Attachment: HIVE-20834.2.patch

> 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, 
> 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)


[jira] [Updated] (HIVE-20834) Hive QueryResultCache entries keeping reference to SemanticAnalyzer from cached query

2018-10-30 Thread Jason Dere (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-20834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dere updated HIVE-20834:
--
Status: Patch Available  (was: Open)

> 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, 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)


[jira] [Updated] (HIVE-20834) Hive QueryResultCache entries keeping reference to SemanticAnalyzer from cached query

2018-10-29 Thread Jason Dere (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-20834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dere updated HIVE-20834:
--
Attachment: HIVE-20834.1.patch

> 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, 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)


[jira] [Updated] (HIVE-20834) Hive QueryResultCache entries keeping reference to SemanticAnalyzer from cached query

2018-10-29 Thread Jason Dere (JIRA)


 [ 
https://issues.apache.org/jira/browse/HIVE-20834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dere updated HIVE-20834:
--
Attachment: dominator_tree.png

> 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: 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)