Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 21 Nov 2012 18:07:58 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1220269748.13256.1353521278621.JavaMail.jiratomcat@arcas>
In-Reply-To: <865960685.119891.1352997612614.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HBASE-7167) Thrift's deleteMultiple() raises
 exception instead of returning list of failed deletes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HBASE-7167?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1350=
2166#comment-13502166 ]=20

Hadoop QA commented on HBASE-7167:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest a=
ttachment=20
  http://issues.apache.org/jira/secure/attachment/12554528/HBASE-7167.patch
  against trunk revision .

    {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 inclu=
de any new or modified tests.
                        Please justify why no new tests are needed for this=
 patch.
                        Also please list what manual steps were performed t=
o verify this patch.

    {color:green}+1 hadoop2.0{color}.  The patch compiles against the hadoo=
p 2.0 profile.

    {color:red}-1 javadoc{color}.  The javadoc tool appears to have generat=
ed 99 warning messages.

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

    {color:red}-1 findbugs{color}.  The patch appears to introduce 24 new F=
indbugs (version 1.3.9) warnings.

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

     {color:red}-1 core tests{color}.  The patch failed these unit tests:
                       org.apache.hadoop.hbase.master.TestSplitLogManager

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/3386//tes=
tReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3386=
//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3386=
//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.=
html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3386=
//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3386=
//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.=
html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3386=
//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3386=
//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3386=
//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.h=
tml
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/3386//c=
onsole

This message is automatically generated.
               =20
> Thrift's deleteMultiple() raises exception instead of returning list of f=
ailed deletes
> -------------------------------------------------------------------------=
-------------
>
>                 Key: HBASE-7167
>                 URL: https://issues.apache.org/jira/browse/HBASE-7167
>             Project: HBase
>          Issue Type: Bug
>          Components: Thrift
>            Reporter: Daniel G=C3=B3mez Ferro
>            Assignee: Daniel G=C3=B3mez Ferro
>         Attachments: HBASE-7167.patch, HBASE-7167.patch
>
>
> Thrift API claims deleteMultiple() returns the list of failed Deletes, bu=
t the current implementation throws a TIOError instead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira