[ https://issues.apache.org/jira/browse/HBASE-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143572#comment-13143572 ]
Hadoop QA commented on HBASE-4553: ---------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12502227/4553-v12.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 24 new or modified tests. -1 javadoc. The javadoc tool appears to have generated -164 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 48 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/164//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/164//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/164//console This message is automatically generated. > The update of .tableinfo is not atomic; we remove then rename > ------------------------------------------------------------- > > Key: HBASE-4553 > URL: https://issues.apache.org/jira/browse/HBASE-4553 > Project: HBase > Issue Type: Task > Reporter: stack > Assignee: stack > Priority: Critical > Fix For: 0.92.0 > > Attachments: 3446-v8.txt, 4553-v10.txt, 4553-v11.txt, 4553-v12.txt, > 4553-v12.txt, 4553-v12.txt, 4553-v5.txt, 4553-v9.txt, > HBase-4553-TestAvroServer.patch > > > This comes of HBASE-4547. The rename in 0.20 hdfs fails if file exists > already. In 0.20+ its better but still 'some' issues if existing reader when > file is renamed. This issue is about fixing this (though we depend on fix > first being in hdfs). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira