Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 26 Apr 2017 22:54:04 +0000 (UTC)
From: "Sean Busbey (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12940735.1455935324000.60677.1493247244316@Atlassian.JIRA>
In-Reply-To: <JIRA.12940735.1455935324000@Atlassian.JIRA>
References: <JIRA.12940735.1455935324000@Atlassian.JIRA> <JIRA.12940735.1455935324561@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HBASE-15296) Break out writer and reader from
 StoreFile
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 26 Apr 2017 22:54:10 -0000


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

Sean Busbey updated HBASE-15296:
--------------------------------
    Status: Open  (was: Patch Available)

(moving out of patch available since the branch-1 version no longer applies)

Can we move doing this for branch-1 into a different JIRA? Presuming we're keeping the incompatible version for master, having both a compatible and incompatible implementation in a single jira makes it harder to disambiguate which branch each relates to.

> Break out writer and reader from StoreFile
> ------------------------------------------
>
>                 Key: HBASE-15296
>                 URL: https://issues.apache.org/jira/browse/HBASE-15296
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>            Reporter: Appy
>            Assignee: Appy
>             Fix For: 2.0.0
>
>         Attachments: HBASE-15296-branch-1.1.patch, HBASE-15296-branch-1.2.patch, HBASE-15296-branch-1.patch, HBASE-15296-branch-1.patch, HBASE-15296-branch-1-v1.patch, HBASE-15296-master.patch, HBASE-15296-master-v2.patch, HBASE-15296-master-v3.patch, HBASE-15296-master-v4.patch, HBASE-15296-master-v5.patch
>
>
> StoreFile.java is trending to become a monolithic class, it's ~1800 lines. Would it make sense to break out reader and writer (~500 lines each) into separate files.
> We are doing so many different things in a single class: comparators, reader, writer, other stuff; and it hurts readability a lot, to the point that just reading through a piece of code require scrolling up and down to see which level (reader/writer/base class level) it belongs to. These small-small things really don't help while trying to understanding the code. There are good reasons we don't do these often (affects existing patches, needs to be done for all branches, etc). But this and a few other classes can really use a single iteration of refactoring to make things a lot better.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)