[
https://issues.apache.org/jira/browse/HADOOP-9517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660321#comment-13660321
]
Steve Loughran commented on HADOOP-9517:
----------------------------------------
Also
h3. User-level file formats.
I'm thinking of {{.har}} here, compression formats etc. The statement here MUST
be, "we will continue to read existing formats, though written data may be in
form that is incompatible with older Hadoop versions". There needs to be tests
for that backwards compatibility too -some files from 1.x in SVN whose contents
are parsed and validated.
h3. Web UI features
No guarantees. If you try to screen scrape the web pages, expect to have to
change with every major release, potentially the minor one. The only way to be
sure of stability is to help define and implement specific machine-parseable
web pages/REST APIs. If you use screen-shots as part of your documentation,
expect to have to update it with every release.
> 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, 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
