[
https://issues.apache.org/jira/browse/PHOENIX-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490727#comment-15490727
]
Hadoop QA commented on PHOENIX-3162:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12828480/PHOENIX-3162_v3.patch
against master branch at commit e4fd03952a15be60eee6ddc557a19ce917c606c2.
ATTACHMENT ID: 12828480
{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:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/575//console
This message is automatically generated.
> TableNotFoundException might be thrown when an index dropped while upserting.
> -----------------------------------------------------------------------------
>
> Key: PHOENIX-3162
> URL: https://issues.apache.org/jira/browse/PHOENIX-3162
> Project: Phoenix
> Issue Type: Bug
> Reporter: Rajeshbabu Chintaguntla
> Assignee: Rajeshbabu Chintaguntla
> Fix For: 4.8.1
>
> Attachments: PHOENIX-3162.patch, PHOENIX-3162_v2.patch,
> PHOENIX-3162_v3.patch
>
>
> If a table has mix of global and local indexes and one of them is dropped
> while upserting data then there is a chance that the query might fail with
> TableNotFoundException. Usually when an index dropped we skip writing to the
> dropped index on failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
