HBase table truncate semantics seems broken as "disable" table is now async by
default.
---------------------------------------------------------------------------------------
Key: HBASE-3269
URL: https://issues.apache.org/jira/browse/HBASE-3269
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.0
Environment: RHEL5 x86_64
Reporter: Suraj Varma
Priority: Critical
The new async design for disable table seems to have caused a side effect on
the truncate command. (IRC chat with jdcryans)
Apparent Cause:
"Disable" is now async by default. When truncate is called, the disable
operation returns immediately and when the drop is called, the disable
operation is still not completed. This results in
HMaster.checkTableModifiable() throwing a TableNotDisabledException.
With earlier versions, disable returned only after Table was disabled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
