[
https://issues.apache.org/jira/browse/HBASE-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595116#comment-13595116
]
Hadoop QA commented on HBASE-7935:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12572392/HBASE-7935-addendum.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4698//console
This message is automatically generated.
> make policy and compactor in default store engine separately pluggable (for
> things like tier-based, and default policy experiments with permutations)
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-7935
> URL: https://issues.apache.org/jira/browse/HBASE-7935
> Project: HBase
> Issue Type: Improvement
> Components: Compaction
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Priority: Minor
> Attachments: HBASE-7935-addendum.patch, HBASE-7935-v0.patch,
> HBASE-7935-v0-with-7843.patch, HBASE-7935-v1.patch, HBASE-7935-v2.patch,
> HBASE-7935-v3.patch, HBASE-7935-v3.patch
>
>
> Technically, StoreEngine can be used to achieve any permutations of things,
> but to make it more convenient to replace compaction policy/compator in
> standard schemes like tier-based, we can add separate hooks in
> DefaultStoreEngine (as long as custom ones conform to its default
> expectations e.g. flat list of sorted files, etc.)
--
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
