hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9517) Define Hadoop Compatibility
Date Wed, 08 May 2013 17:57:17 GMT

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

Steve Loughran commented on HADOOP-9517:
----------------------------------------

This looks pretty good - I like where you list out "no policy here" -which is both a warning
and a sign of where work may be needed at some point in the future.

I'd flag on the {{Currently, there is NO policy on preserving data formats across releases.}}
as while that may be the case,; HDFS does have a policy of handling migration from at least
one major version behind. The format may change, but the data will be preserved. Can you add
that to avoid scaring people?
                
> Define Hadoop Compatibility
> ---------------------------
>
>                 Key: HADOOP-9517
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9517
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: documentation
>            Reporter: Arun C Murthy
>            Assignee: Karthik Kambatla
>         Attachments: hadoop-9517.patch, hadoop-9517.patch
>
>
> As we get ready to call hadoop-2 stable we need to better define 'Hadoop Compatibility'.
> http://wiki.apache.org/hadoop/Compatibility is a start, let's document requirements clearly
and completely.

--
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

Mime
View raw message