[
https://issues.apache.org/jira/browse/PHOENIX-5788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17064134#comment-17064134
]
Hadoop QA commented on PHOENIX-5788:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12997344/PHOENIX-5788.PHOENIX-5748-4.x-HBase-1.5.001.patch
against 4.x-HBase-1.5 branch at commit
264715133cdb8085b48a79eddfe3d27736614715.
ATTACHMENT ID: 12997344
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3626//console
This message is automatically generated.
> Handling deletes on non-existing rows
> -------------------------------------
>
> Key: PHOENIX-5788
> URL: https://issues.apache.org/jira/browse/PHOENIX-5788
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Kadir OZDEMIR
> Assignee: Kadir OZDEMIR
> Priority: Major
> Attachments: PHOENIX-5788.PHOENIX-5748-4.x-HBase-1.5.001.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> PHOENIX-5709 skips generating index delete mutations if the data table rows
> (and thus the index table rows) do not exist. However, it allows the delete
> mutations to be applied on the data table. This does not create a data
> integrity problem but creates an extra case to handle for the inline
> verification implementation to consider. PHOENIX-5709 currently does not
> handle this case. We should either apply these delete statements to both
> tables or apply none of them.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
