Mailing-List: contact pig-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: pig-dev@hadoop.apache.org
Message-ID: <331089875.377531269039147311.JavaMail.jira@brutus.apache.org>
Date: Fri, 19 Mar 2010 22:52:27 +0000 (UTC)
From: "Alan Gates (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Subject: [jira] Commented: (PIG-1311) Pig interfaces should be clearly
 classified in terms of scope and stability
In-Reply-To: <906411638.377401269038787254.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/PIG-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847632#action_12847632 ] 

Alan Gates commented on PIG-1311:
---------------------------------

Hadoop has a proposal on how to approach this in HADOOP-5073

I propose we use the same nomenclature.  Java interfaces would be marked via annotations (provided by Hadoop commons).  For other interfaces we would need to provide version specific documents (that is, in forrest not in wiki) that detail scope and stability for each interface.

> Pig interfaces should be clearly classified in terms of scope and stability
> ---------------------------------------------------------------------------
>
>                 Key: PIG-1311
>                 URL: https://issues.apache.org/jira/browse/PIG-1311
>             Project: Pig
>          Issue Type: Improvement
>            Reporter: Alan Gates
>            Assignee: Alan Gates
>
> Clearly marking Pig interfaces (Java interfaces but also things like config files, CLIs, Pig Latin syntax and semantics, etc.) to show scope (public/private) and stability (stable/evolving/unstable) will help users understand how to interact with Pig and developers to understand what things they can and cannot change.

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