Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3CAA710EE5 for ; Mon, 5 Aug 2013 19:22:54 +0000 (UTC) Received: (qmail 90699 invoked by uid 500); 5 Aug 2013 19:22:52 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 90001 invoked by uid 500); 5 Aug 2013 19:22:51 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 89833 invoked by uid 99); 5 Aug 2013 19:22:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Aug 2013 19:22:48 +0000 Date: Mon, 5 Aug 2013 19:22:48 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-9127) HFileContext MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Andrew Purtell created HBASE-9127: ------------------------------------- Summary: HFileContext Key: HBASE-9127 URL: https://issues.apache.org/jira/browse/HBASE-9127 Project: HBase Issue Type: Improvement Reporter: Andrew Purtell 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 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