[
https://issues.apache.org/jira/browse/HBASE-17527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838290#comment-15838290
]
Josh Elser commented on HBASE-17527:
------------------------------------
bq. 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
Cool. Wasn't sure if you were suggesting something global (e.g. could also be
picked up by normal CLI tools -- ImportTsv, `hbase shell`) or if your
suggestion was limited to the ITs (and thus Tool is appropriate). You already
answered my follow-on :)
bq. From above discussion, I interpret that such practice should not be
continued in the future.
I would agree with ya.
bq. Maybe add a new method in IntegrationTestBase which would be called at the
end of table creation by various IT classes ?
That introduces a bit of debt too. Everyone has to remember/know to use that
method instead.
Would it be possible to wrap the {{HBaseAdmin}} returned by
{{HBaseTestingUtility}} to transparently modify the HTD/HCD on creation? Would
need to dig a bit deeper into the usage...
> 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)
