Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 27 Apr 2015 22:50:40 +0000 (UTC)
From: "Keith Turner (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12824438.1430173227000.44542.1430175040130@Atlassian.JIRA>
In-Reply-To: <JIRA.12824438.1430173227000@Atlassian.JIRA>
References: <JIRA.12824438.1430173227000@Atlassian.JIRA>
 <JIRA.12824438.1430173227863@arcas>
Subject: [jira] [Commented] (ACCUMULO-3756) RangeInputSplit extends non
 public class
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Keith Turner commented on ACCUMULO-3756:
----------------------------------------

Much of the Accumulo map reduce implementation is in the Accumulo public API.  I am mulling over the idea of deprecating all M/R implementation code in 1.7.0 and only supporting the M/R impl code that was present in 1.6.  Note I am not thinking of deprecating code needed to simply read and write from Accumulo using map reduce, just things like protected inner classes that implement RecordReader.   Also thinking of moving all of the actual implementation code to a new impl package.  The goal would be to make things easier to understand, make the code easier to maintain, and make it easier to add features in the future.   I am still researching this idea and I am not yet sure about the concept.  Not even sure if would work at this point.  If anyone has any thoughts, I would like to hear them.  

I think one of the original intentions of exposing implementation code in the API was that it would allow users to extends Accumulo's input and output formats.  The primary mechanism for exposing implementation details is protected methods as extension points.  It seems like the pattern is to deprecate some extension points when adding new features, and I don't think this is working so well.  Its a bit of a mess now.  I don't have a lot of confidence in the correctness of the deprecated extension points.  An alternative to this extension point model, is one of pushing changes to the Accumulo M/R implementation like ACCUMULO-3602 and ACCUMULO-391 did.


> RangeInputSplit extends non public class
> ----------------------------------------
>
>                 Key: ACCUMULO-3756
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3756
>             Project: Accumulo
>          Issue Type: Sub-task
>            Reporter: Keith Turner
>            Assignee: Keith Turner
>             Fix For: 1.7.0
>
>
> While working on ACCUMULO-3657, I realized that RangeInputSplit now extends a non public API class. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)