hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-7978) Merge hbase-prefixtree into hbase-server
Date Mon, 06 Nov 2017 06:18:01 GMT

     [ https://issues.apache.org/jira/browse/HBASE-7978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack resolved HBASE-7978.
--------------------------
    Resolution: Won't Fix

hbase-prefix-tree was removed in hbase2. Resolving as won't fix.

> 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.98.0, 0.95.0
>            Reporter: Enis Soztutar
>
> I would like to discuss the possibility of merging the prefix tree module into the hbase-server
module. 
> 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 was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message