There are a number of APIs that came in with MOB that are not new actions for HBase, simply new actions for a MOB implementation:
And in HBaseAdmin:
Remove these special cases from the Admin API where possible by folding them into existing APIs.
We definitely don't need one method for a singleton and another for collections.
Ideally we will not have any APIs named *Mob when finished, whether MOBs are in use on a table or not should be largely an internal detail. Exposing as schema option would be fine, this conforms to existing practice for other features.
Marking critical because I think removing the *Mob special cased APIs should be a precondition for release of this feature either in 2.0 or as a backport.