hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7236) add per-table/per-cf configuration via metadata
Date Tue, 09 Apr 2013 00:46:17 GMT

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

Sergey Shelukhin commented on HBASE-7236:
-----------------------------------------

I am going to unlink the subtask for conversion of legacy metadata, and resolve this.
The feature was added, let legacy metadata remain legacy metadata
                
> add per-table/per-cf configuration via metadata
> -----------------------------------------------
>
>                 Key: HBASE-7236
>                 URL: https://issues.apache.org/jira/browse/HBASE-7236
>             Project: HBase
>          Issue Type: Umbrella
>    Affects Versions: 0.95.2
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>         Attachments: HBASE-7236-PROTOTYPE.patch, HBASE-7236-PROTOTYPE.patch, HBASE-7236-PROTOTYPE-v1.patch,
HBASE-7236-v0.patch, HBASE-7236-v1.patch, HBASE-7236-v2.patch, HBASE-7236-v3.patch, HBASE-7236-v4.patch,
HBASE-7236-v5.patch, HBASE-7236-v6.patch, HBASE-7236-v6.patch
>
>
> Regardless of the compaction policy, it makes sense to have separate configuration for
compactions for different tables and column families, as their access patterns and workloads
can be different. In particular, for tiered compactions that are being ported from 0.89-fb
branch it is necessary to have, to use it properly.
> We might want to add support for compaction configuration via metadata on table/cf.

--
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

Mime
View raw message