You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Mikhail Bautin (JIRA)" <ji...@apache.org> on 2012/06/22 21:27:42 UTC
[jira] [Comment Edited] (HBASE-6226) move DataBlockEncoding and
related classes to hbase-common module
[ https://issues.apache.org/jira/browse/HBASE-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399505#comment-13399505 ]
Mikhail Bautin edited comment on HBASE-6226 at 6/22/12 7:26 PM:
----------------------------------------------------------------
Data block encoding is a server-side feature, but putting it in hbase-common will make it available to clients, right? What is the desired dependency graph between hbase-server, hbase-common, and hbase-<data_block_encodingX> components?
was (Author: mikhail):
Data block encoding is a server-side feature, so putting it in hbase-common will make it available to clients, right? What is the desired dependency graph between hbase-server, hbase-common, and hbase-<data_block_encodingX> components?
> move DataBlockEncoding and related classes to hbase-common module
> -----------------------------------------------------------------
>
> Key: HBASE-6226
> URL: https://issues.apache.org/jira/browse/HBASE-6226
> Project: HBase
> Issue Type: Improvement
> Components: io, regionserver
> Affects Versions: 0.96.0
> Reporter: Matt Corgan
> Assignee: Matt Corgan
> Attachments: HBASE-6226-v1.patch
>
>
> In order to isolate the implementation details of HBASE-4676 (PrefixTrie encoding) and other DataBlockEncoders by putting them in modules, this pulls up the DataBlockEncoding related interfaces into hbase-common.
> No tests are moved in this patch. The only notable change was trimming a few dependencies on HFileBlock which adds dependencies to much of the regionserver.
> The test suite passes locally for me.
> I tried to keep it as simple as possible... let me know if there are any concerns.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira