[ https://issues.apache.org/jira/browse/HBASE-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144217#comment-13144217 ]
Hadoop QA commented on HBASE-4741: ---------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12502464/4741-v4.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 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 46 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: org.apache.hadoop.hbase.thrift2.TestThriftHBaseServiceHandler org.apache.hadoop.hbase.client.TestAdmin org.apache.hadoop.hbase.coprocessor.TestMasterObserver org.apache.hadoop.hbase.master.TestDistributedLogSplitting org.apache.hadoop.hbase.master.TestMasterFailover Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/172//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/172//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/172//console This message is automatically generated. > Online schema change doesn't return errors > ------------------------------------------ > > Key: HBASE-4741 > URL: https://issues.apache.org/jira/browse/HBASE-4741 > Project: HBase > Issue Type: Bug > Affects Versions: 0.92.0 > Reporter: Jean-Daniel Cryans > Priority: Critical > Fix For: 0.92.0 > > Attachments: 4741-v2.txt, 4741-v3.txt, 4741-v4.txt, 4741.txt > > > Still after the fun I had over in HBASE-4729, I tried to finish altering my > table (remove a family) since only half of it was changed so I did this: > {quote} > hbase(main):002:0> alter 'TestTable', NAME => 'allo', METHOD => 'delete' > Updating all regions with the new schema... > 244/244 regions updated. > Done. > 0 row(s) in 1.2480 seconds > {quote} > Nice it all looks good, but over in the master log: > {quote} > org.apache.hadoop.hbase.InvalidFamilyOperationException: Family 'allo' does > not exist so cannot be deleted > at > org.apache.hadoop.hbase.master.handler.TableDeleteFamilyHandler.handleTableOperation(TableDeleteFamilyHandler.java:56) > at > org.apache.hadoop.hbase.master.handler.TableEventHandler.process(TableEventHandler.java:86) > at > org.apache.hadoop.hbase.master.HMaster.deleteColumn(HMaster.java:1011) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.hadoop.hbase.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:348) > at > org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1242) > {quote} > Maybe we should do checks before launching the async task. > Marking critical as this is a regression. -- 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