Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <1265224706.1253909716088.JavaMail.jira@brutus>
Date: Fri, 25 Sep 2009 13:15:16 -0700 (PDT)
From: "Sanjay Radia (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-5073) Hadoop 1.0 Interface Classification
 - scope (visibility - public/private) and stability
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-5073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759723#action_12759723 ] 

Sanjay Radia commented on HADOOP-5073:
--------------------------------------

Proposed Classification for Hadoop Interfaces (updated)
* Scope Public
** Deprecated
*** FileSystem, mapred
** Stable
*** FileContext, MapReduce, Config, CLI (inlcuding output), Job Logs API, Audit logs
*** AbstractFileSystem (targeted  for implementers of filesystems,  not for application use)
*** parts of Mapred.lib (have we decided which parts?)
*** parts of instrumentation metrics (have we decided which parts?)
** Evolving
*** TFile, jmx interface (till it becomes stable),
*** parts of Mapred.lib (have we decided which parts?)
*** parts of instrumentation metrics (have we decided which parts?)
*** Job logs and job history ( Some tools, scripts and chukwa use this to analyze job processing)
** Not An interface
*** Web GUI
* Scope Private
** Limited-Private Evolving
*** RPC, Metrics API, (HDFS-MapReduce Private) - once stable, we can consider making these public-stable.PIU
*** Security APIs
** Project-Private Stable
*** Intra-HDFS and MR protocols (facilitates rolling upgrades down the road)
*** Mapreduce's context object implementation class
*** FSImage
**** Note this will enable old versions of HDFS to read newer fsImage and hence enable more flexible roll backs.
**** Q. Should this be Project-Private Evolving instead?
**** Regardless of the stability of FSImage, new versions of HDFS have to be able to transparently convert older versions and provide roll-back.
** Project-Private Evolving
*** DFSClient (Q. should this be "project-private unstable")
** Project-Private Unstable
*** System logs
*** All implementation classes and interfaces not otherwise classified are considered to be project-private unstable.


> Hadoop 1.0 Interface Classification - scope (visibility - public/private) and stability
> ---------------------------------------------------------------------------------------
>
>                 Key: HADOOP-5073
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5073
>             Project: Hadoop Common
>          Issue Type: Sub-task
>    Affects Versions: 0.21.0
>            Reporter: Sanjay Radia
>            Assignee: Jakob Homan
>             Fix For: 0.21.0
>
>         Attachments: 5073_demo.png, c5073_20090825.patch, c5073_20090825.png, COMMON-5073.patch, COMMON-5073.patch, COMMON-5073.patch, HADOOP-5073.patch, Nested.png, Picture 1.png
>
>
> This jira proposes an interface classification for hadoop interfaces.
> The discussion was started in email alias core-dev@hadoop.apache.org in Nov 2008.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.