[ https://issues.apache.org/jira/browse/PHOENIX-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180290#comment-16180290 ]
Hadoop QA commented on PHOENIX-4224: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12888990/PHOENIX-4224-1.patch against master branch at commit 944bed73585a5ff826997895c2da43720b229d8a. ATTACHMENT ID: 12888990 {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 lineLengths{color}. The patch introduces the following lines longer than 100: + QueryServices.MAX_SERVER_CACHE_TIME_TO_LIVE_MS_ATTRIB, QueryServicesOptions.DEFAULT_MAX_SERVER_CACHE_TIME_TO_LIVE_MS); + return true; // cache was send more than maxTTL ms ago, expecting that it's expired {color:red}-1 core tests{color}. The patch failed these unit tests: ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.UpsertValuesIT Test results: https://builds.apache.org/job/PreCommit-PHOENIX-Build/1478//testReport/ Console output: https://builds.apache.org/job/PreCommit-PHOENIX-Build/1478//console This message is automatically generated. > Automatic resending cache for HashJoin doesn't work when cache has expired on > server side > ------------------------------------------------------------------------------------------ > > Key: PHOENIX-4224 > URL: https://issues.apache.org/jira/browse/PHOENIX-4224 > Project: Phoenix > Issue Type: Bug > Affects Versions: 4.12.0 > Reporter: Sergey Soldatov > Assignee: Sergey Soldatov > Priority: Blocker > Fix For: 4.12.0 > > Attachments: PHOENIX-4224-1.patch > > > The problem occurs when the cache has expired on server side and client want > to resend it. This problem has been introduced in PHOENIX-4010. Actual result > in this case is that client doesn't send the cache because of the following > check: > {noformat} > if (cache.addServer(tableRegionLocation) ... )) { > success = addServerCache(table, > startkeyOfRegion, pTable, cacheId, cache.getCachePtr(), cacheFactory, > txState); > } > {noformat} > Since the region location hasn't been changed, we actually don't send cache > again, but produce new scanner which will fail with the same error and client > will fall to recursion. -- This message was sent by Atlassian JIRA (v6.4.14#64029)