hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17527) Allow IntegrationTestBigLinkedList table to be in memory compacted
Date Wed, 25 Jan 2017 17:48:26 GMT

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

stack commented on HBASE-17527:
-------------------------------

Hey [~elserj]

bq. Suggestions on how you'd expect to see this controlled by users, stack?

I've not spent much time thinking on it [~elserj] but since you ask (smile), yeah, IT is a
Tool... it has the -D facility for setting java properties (exploited by this hack)... It'd
be cool if an interceptor could pick out changes for HTD/HCD (we already have HBaseAbstractTool
in place as a good home for this sort of malarky) and then set the properties on IT table
HTD/HCD post creation. For it to work, I'd think that the passed in args would have to be
the actual names of the HTD/HCD properties -- not new variable name inventions and capitalization
as here; i.e. IN_MEMORY_COMPACTION rather than inMemoryCompaction.

Just a suggestion. Go easy [~elserj]

> Allow IntegrationTestBigLinkedList table to be in memory compacted
> ------------------------------------------------------------------
>
>                 Key: HBASE-17527
>                 URL: https://issues.apache.org/jira/browse/HBASE-17527
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ted Yu
>         Attachments: 17527.v1.txt, 17527.v2.txt
>
>
> Currently IntegrationTestBigLinkedList table doesn't support specification of in memory
compaction scheme.
> This JIRA is to add support for specifying different in memory compaction policies.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message