hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13734) Improper timestamp checking with VisibilityScanDeleteTracker
Date Sat, 23 May 2015 11:42:17 GMT

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

Hadoop QA commented on HBASE-13734:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12735001/HBASE-13734-branch-1.patch
  against branch-1 branch at commit e93e1ea73c6ce5f632636c613068ddd877ebb60d.
  ATTACHMENT ID: 12735001

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified
tests.

    {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions
(2.4.1 2.5.2 2.6.0)

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 protoc{color}.  The applied patch does not increase the total number of
protoc compiler warnings.

    {color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 1 warning messages.

    {color:green}+1 checkstyle{color}.  The applied patch does not increase the total number
of checkstyle errors

    {color:green}+1 findbugs{color}.  The patch does not introduce any  new Findbugs (version
2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines longer than 100

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/14160//testReport/
Release Findbugs (version 2.0.3) 	warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/14160//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/14160//artifact/patchprocess/checkstyle-aggregate.html

  Javadoc warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/14160//artifact/patchprocess/patchJavadocWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/14160//console

This message is automatically generated.

> Improper timestamp checking with VisibilityScanDeleteTracker
> ------------------------------------------------------------
>
>                 Key: HBASE-13734
>                 URL: https://issues.apache.org/jira/browse/HBASE-13734
>             Project: HBase
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 0.98.4
>            Reporter: Anoop Sam John
>            Assignee: Anoop Sam John
>             Fix For: 2.0.0, 0.98.14, 1.0.2, 1.2.0, 1.1.1
>
>         Attachments: HBASE-13734-branch-1.patch, HBASE-13734.patch
>
>
> 3 issues
> 1. When VC is used and all the put cells and delete cells are not having any visibility
associated with them, we are not correctly checking put cells ts against that of delete cell
resulting in deletion of cells coming in after the delete ts
> 2. Have a row r1 with 2 cells of same TS but different visibility. In order to delete
both cells we have to apply 2 deletes with these 2 visibility being set to Delete. We are
trying to do this using delete full row option or delete cf way. But only one cell is getting
deleted.
> 3. Same case as in #2 when I try to delete using family version delete, only one cell
is getting deleted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message