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 2013/09/20 19:05:53 UTC

[jira] [Updated] (HBASE-9595) HStore should use HFileContext for holding the state therein rather than duplicating it

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

Andrew Purtell updated HBASE-9595:
----------------------------------

    Priority: Minor  (was: Major)
    
> HStore should use HFileContext for holding the state therein rather than duplicating it
> ---------------------------------------------------------------------------------------
>
>                 Key: HBASE-9595
>                 URL: https://issues.apache.org/jira/browse/HBASE-9595
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Andrew Purtell
>            Assignee: ramkrishna.s.vasudevan
>            Priority: Minor
>
> Currently at the Store level, HFileContext is created on demand using HStore state when HFile readers or writers are created. We can't create a HFileContext at store creation time and carry long term state within. Therefore we can't avoid adding more members to HStore even if we have already added a new member to HFileContext. This partially defeats why HFileContext is a good idea: It can/should encapsulate the state passed between Store and HFile so additions don't require new members to various Store and HFile classes.

--
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