[ 
https://issues.apache.org/jira/browse/HBASE-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506795#comment-13506795
 ] 

Andrew Purtell commented on HBASE-7055:
---------------------------------------

bq. CompactionConfiguration is base compaction config, it is not just 
xml-based, it uses runtime store-specific settings. TierBased one adds more on 
top of that; it seems that Tier-stuff doesn't belong to the main 
CompactionConfiguration; and main CompactionConfiguration is not as simple as 
generic Configuration. It's also Store (e.g. region/cf) specific.

Up to now we've had two distinct and cleanly separable configuration 
mechanisms. The heavyweight Configuration which carries global, and currently 
static configuration, and the table and column descriptors that can be CF 
specific by definition and updated at runtime without requiring a process 
restart. Pardon if I've misunderstood but mixing these would blur static and 
dynamic configuration and that doesn't seem a good design option. 
                
> port HBASE-6371 tier-based compaction from 0.89-fb to trunk - first slice 
> (not configurable by cf or dynamically)
> -----------------------------------------------------------------------------------------------------------------
>
>                 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, 
> HBASE-6371-v3-refactor-only-squashed.patch, 
> HBASE-6371-v4-refactor-only-squashed.patch, 
> HBASE-6371-v5-refactor-only-squashed.patch, HBASE-7055-v0.patch, 
> HBASE-7055-v1.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

Reply via email to