[
https://issues.apache.org/jira/browse/HBASE-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488195#comment-13488195
]
Sergey Shelukhin commented on HBASE-7055:
-----------------------------------------
We discussed with Enis and it seems like this kind of configuration should be
stored on table and column family level; either with some explicit system
parameters, or as a blob (similar to the storing-HCat/etc.-metadata ideas),
depending on how we thing about different compaction policies (system provides
a set e.g. the tiered one vs the default one, or they are more
pluggable/user-changeable).
Another issue is that the new policy is configured on by default in the xml
config (I missed that), which seems premature since use cases are not 100%
clear, in a sense that people might have different scenarios for what
constitutes old data/hot data/lots of data, so it's hard to come up with
reasonable tier defaults.
I will recall the patch for now...
> port HBASE-6371 tier-based compaction from 0.89-fb to trunk
> -----------------------------------------------------------
>
> Key: HBASE-7055
> URL: https://issues.apache.org/jira/browse/HBASE-7055
> Project: HBase
> Issue Type: Task
> Components: Compaction
> Affects Versions: 0.96.0
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Fix For: 0.96.0
>
> Attachments: HBASE-6371-squashed.patch, HBASE-6371-v2-squashed.patch
>
>
> There's divergence in the code :(
> See HBASE-6371 for details.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
