You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2014/05/12 05:47:17 UTC

[jira] [Resolved] (HBASE-9127) HFileContext

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

Andrew Purtell resolved HBASE-9127.
-----------------------------------

          Tags:   (was: 0.96notable)
    Resolution: Fixed

This was introduced as part of HFile V3

> HFileContext
> ------------
>
>                 Key: HBASE-9127
>                 URL: https://issues.apache.org/jira/browse/HBASE-9127
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>         Attachments: 0001-Introduce-HFileContext.patch, 0002-Move-compression-algorithm-into-HFileContext.patch, 0003-Move-data-block-encoder-into-HFileContext.patch
>
>
> We can roll up at least some of the state we are leaking between the Store layer and the HFile layer by introducing an IO context for passing between the two. This idea has come up in other discussions. Here I am calling it 'HFileContext' because the particulars are regarding how to configure HFile readers and writers. This will be easier to maintain than various and sundry method parameters and (duplicated) instance variables sprinkled about, and will make adding or modifying persistence features easier and less disruptive.



--
This message was sent by Atlassian JIRA
(v6.2#6252)