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

Hudson commented on PHOENIX-85:
-------------------------------

FAILURE: Integrated in Apache Phoenix - Branch:4.0 #35 (See 
[https://builds.apache.org/job/Phoenix-4.0/35/])
PHOENIX-85 Refine error handling in HashJoinPlan execution and add warnings 
(maryannxue: rev d61d6b44f3f67e642b3097f475d0d1c344713428)
* phoenix-core/src/main/java/org/apache/phoenix/cache/TenantCacheImpl.java
* phoenix-core/src/main/java/org/apache/phoenix/memory/GlobalMemoryManager.java
* 
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/HashJoinRegionScanner.java
* phoenix-core/src/main/java/org/apache/phoenix/cache/ServerCacheClient.java
* phoenix-core/src/main/java/org/apache/phoenix/execute/HashJoinPlan.java


> Refine error handling in HashJoinPlan execution and add warnings
> ----------------------------------------------------------------
>
>                 Key: PHOENIX-85
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-85
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 3.0.0
>            Reporter: Maryann Xue
>            Assignee: Maryann Xue
>            Priority: Trivial
>             Fix For: 3.0.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Remove all hash cache spontaneously if any of the sub-query execution raises 
> an exception.
> Compare the end time of each sub-query execution with the earliest finished 
> sub-query execution. If the time difference is greater than the "max server 
> cache live time", warn users that the earlier hash caches on the server might 
> have expired and have been removed.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to