Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 7 Nov 2012 21:52:17 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <991046159.83572.1352325137346.JavaMail.jiratomcat@arcas>
In-Reply-To: <472861939.29651.1351201992558.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HBASE-7055) port HBASE-6371 tier-based
 compaction from 0.89-fb to trunk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-7055:
------------------------------

bq. Are we good with porting it without dynamic config updates, with cf-specific config stored on CF, and off by default?

That could be good.  Do you think this new mechanism will be used?  Its objective is 'more fine-grained control' according to the pdf Liyin just posted.  Have you tried it Sergey?  Does it give good feedback if misconfigured?  Is this feature of any use if its not configurable at runtime: i.e. does having to take the table offline to change a param make this improvement moot until we have dynamic config?


> 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, HBASE-6371-v3-refactor-only-squashed.patch, HBASE-6371-v4-refactor-only-squashed.patch, HBASE-6371-v5-refactor-only-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