[
https://issues.apache.org/jira/browse/HBASE-14227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701027#comment-14701027
]
Heng Chen commented on HBASE-14227:
-----------------------------------
{quote}
1. Use a special name format in the cf name, if we want to do the mobCompact,
we can pass in a special cf name, for instance cf$MOB.
{quote}
There is no need to do this. If CF is passed in, we can check schema option to
decide whether the CF is MOB or not.
The question is when compact on table or region Level, shall we do MOB
compaction?
If we do, the function {{Admin.compact(final TableName tableName)}} need one
additional parameter to switch the mob compaction and normal compaction as
[~jingcheng...@intel.com] said.
If we don't, there is no need to change {{Admin.compact(final TableName
tableName)}}
> Fold special cased MOB APIs into existing APIs
> ----------------------------------------------
>
> Key: HBASE-14227
> URL: https://issues.apache.org/jira/browse/HBASE-14227
> Project: HBase
> Issue Type: Task
> Components: mob
> Affects Versions: 2.0.0
> Reporter: Andrew Purtell
> Priority: Blocker
> Fix For: 2.0.0
>
>
> 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:
> - compactMob
> - compactMobs
> - majorCompactMob
> - majorCompactMobs
> - getMobCompactionState
> And in HBaseAdmin:
> - validateMobColumnFamily
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
