[
https://issues.apache.org/jira/browse/PHOENIX-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562204#comment-15562204
]
Hadoop QA commented on PHOENIX-2935:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12832459/PHOENIX-2935.patch
against master branch at commit ad99952792b8b119085499d8d0d734c3d2dc053b.
ATTACHMENT ID: 12832459
{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:red}-1 javadoc{color}. The javadoc tool appears to have generated
38 warning messages.
{color:red}-1 release audit{color}. The applied patch generated 1 release
audit warnings (more than the master's current 0 warnings).
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+
context.getScan().setAttribute(PhoenixIndexCodec.INDEX_MD, ptr.get());
+
context.getScan().setAttribute(BaseScannerRegionObserver.TX_STATE, txState);
+ final long mutationCount =
(Long)aggProjector.getColumnProjector(0).getValue(row,
+ long blockingMemstoreSize, byte[] indexMaintainersPtr, byte[]
txState) throws IOException {
+ commitBatch(region, mutations, indexUUID,
blockingMemStoreSize, indexMaintainersPtr, txState);
+ commitBatch(region, indexMutations, null,
blockingMemStoreSize, null, txState);
+ commitBatch(region,mutations, indexUUID,
blockingMemStoreSize, indexMaintainersPtr, txState);
+ String msg = "key=" + ServerCacheClient.idToString(uuid) + "
region=" + env.getRegion() + "host="
+ SQLException e = new
SQLExceptionInfo.Builder(SQLExceptionCode.INDEX_METADATA_NOT_FOUND).setMessage(msg)
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/620//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/620//artifact/patchprocess/patchReleaseAuditWarnings.txt
Javadoc warnings:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/620//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/620//console
This message is automatically generated.
> IndexMetaData cache can expire when a delete and or query running on server
> ---------------------------------------------------------------------------
>
> Key: PHOENIX-2935
> URL: https://issues.apache.org/jira/browse/PHOENIX-2935
> Project: Phoenix
> Issue Type: Bug
> Reporter: Ankit Singhal
> Assignee: Ankit Singhal
> Labels: index
> Fix For: 4.9.0
>
> Attachments: PHOENIX-2935.patch
>
>
> IndexMetaData cache can expire when a delete or upsert query is running on
> server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)