hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7978) Merge hbase-prefixtree into hbase-server
Date Sat, 02 Mar 2013 03:25:12 GMT

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

Ted Yu commented on HBASE-7978:

bq. stay away from hadoop trunk's one-module-per-package policy
Can you cite some literature supporting the above view ?

>From my understanding, usage of prefix-tree targets specific scenario where random read
performance is critical but write patch can tolerate some latency. When prefix-tree was first
proposed, our modularization was far from the current status. A lot of work has gone in so
that the inclusion of prefix-tree has minimal impact on the rest of the code base.
> Merge hbase-prefixtree into hbase-server
> ----------------------------------------
>                 Key: HBASE-7978
>                 URL: https://issues.apache.org/jira/browse/HBASE-7978
>             Project: HBase
>          Issue Type: Improvement
>          Components: HFile
>    Affects Versions: 0.95.0, 0.98.0
>            Reporter: Enis Soztutar
> I would like to discuss the possibility of merging the prefix tree module into the hbase-server
> Ideally, I think we should have hbase-mapreduce and hbase-storage modules, the latter
one containing most of HFile code. hbase-mapreduce depends on hbase-storage so that it knows
how to encode hfiles. prefix-tree belongs to hbase-storage. 
> prefix tree is just another DBE, although a big one, and it rightfully belongs with her
sisters. The fact that the code is independent from the rest of the code base does not mean
that it should have it's own module. We should keep the number of modules manageable, and
stay away from hadoop trunk's one-module-per-package policy. 
> Related: HBASE-7936

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

View raw message