hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2246) In CHANGES.txt, move HADOOP-1851 & HADOOP-1231 to INCOMPATIBLE CHANGES section
Date Fri, 23 Nov 2007 09:39:43 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544952

Arun C Murthy commented on HADOOP-2246:

bq. Strictly speaking, HADOOP-1231 isn't a incompatible change. 

The conclusion that Doug, Owen and I came to during an offline discussion is that:
a) Deprecating code doesn't mean it is an incompatible change.
b) Removal of deprecated code means that the change is incompatible.

What do others think?

> In CHANGES.txt, move HADOOP-1851 & HADOOP-1231 to INCOMPATIBLE CHANGES section
> ------------------------------------------------------------------------------
>                 Key: HADOOP-2246
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2246
>             Project: Hadoop
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 0.15.0
>            Reporter: Devaraj Das
>            Assignee: Arun C Murthy
>            Priority: Blocker
>             Fix For: 0.15.1
>         Attachments: 2246.patch, HADOOP-2246_2_20071123.patch
> HADOOP-1851 redefines the way one would control compression for the intermediate and
the final outputs of a job. HADOOP-1231 adds Generics to the framework and user code should
be aware of that (at least for code that requires compilation with 0.15). In CHANGES.txt these
two appear in NEW FEATURES and IMPROVEMENTS sections respectively. Ideally, they should be
part of the INCOMPATIBLE CHANGES section.

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

View raw message