You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2017/08/03 00:58:00 UTC

[jira] [Commented] (HBASE-15069) Unify HFile Writer and Reader creation patterns

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

stack commented on HBASE-15069:
-------------------------------

Unscheduling. Bring back in if starts to make progress again. This would be nice to have.

> Unify HFile Writer and Reader creation patterns
> -----------------------------------------------
>
>                 Key: HBASE-15069
>                 URL: https://issues.apache.org/jira/browse/HBASE-15069
>             Project: HBase
>          Issue Type: Bug
>          Components: HFile
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hsieh
>            Assignee: Jonathan Hsieh
>         Attachments: hbase-15069.patch, hbase-15069.v2.patch, hbase-15069.v3.patch, hbase-15069.v4b.patch, hbase-15069.v4.patch
>
>
> There are a plethora of different static methods sprinkled through out HStoreFile and HFile, and many tests that have extraneous calls to 'new CacheConfig(conf)' or essentially extraneous FileSystem arguments threaded through out the code.
> This patch forces all creation to go through HFile Reader and Writer Builders, eliminates all static Builder constructors, and limits the exposure Reader/Writers .  It also forces all HFile writer uses outside of the o.a.h.h.io.hfile package to use the StoreFile writers



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)