Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 648 invoked from network); 18 Dec 2007 23:56:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Dec 2007 23:56:05 -0000 Received: (qmail 43321 invoked by uid 500); 18 Dec 2007 23:55:53 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 43284 invoked by uid 500); 18 Dec 2007 23:55:53 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 43275 invoked by uid 99); 18 Dec 2007 23:55:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Dec 2007 15:55:53 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Dec 2007 23:55:39 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 3F6C071428F for ; Tue, 18 Dec 2007 15:55:43 -0800 (PST) Message-ID: <13268107.1198022143257.JavaMail.jira@brutus> Date: Tue, 18 Dec 2007 15:55:43 -0800 (PST) From: "Konstantin Shvachko (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Commented: (HADOOP-2404) HADOOP-2185 breaks compatibility with hadoop-0.15.0 In-Reply-To: <22781223.1197372523409.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552940 ] Konstantin Shvachko commented on HADOOP-2404: --------------------------------------------- Do you propose to introduce here per-parameter (back-compatible) methods only for the affected address and port parameters or for all of them? The latter is a big change presumably to be addressed by HADOOP-2385 after a reasonable design effort. Backward compatibility for port parameters is a more urgent and much less permanent matter. > HADOOP-2185 breaks compatibility with hadoop-0.15.0 > --------------------------------------------------- > > Key: HADOOP-2404 > URL: https://issues.apache.org/jira/browse/HADOOP-2404 > Project: Hadoop > Issue Type: Bug > Components: conf > Affects Versions: 0.16.0 > Reporter: Arun C Murthy > Assignee: Konstantin Shvachko > Priority: Blocker > Fix For: 0.16.0 > > Attachments: ConfigurationConverter.patch > > > HADOOP-2185 removed the following configuration parameters: > {noformat} > dfs.secondary.info.port > dfs.datanode.port > dfs.info.port > mapred.job.tracker.info.port > tasktracker.http.port > {noformat} > and changed the following configuration parameters: > {noformat} > dfs.secondary.info.bindAddress > dfs.datanode.bindAddress > dfs.info.bindAddress > mapred.job.tracker.info.bindAddress > mapred.task.tracker.report.bindAddress > tasktracker.http.bindAddress > {noformat} > without a backward-compatibility story. > Lots are applications/cluster-configurations are prone to fail hence, we need a way to keep things working as-is for 0.16.0 and remove them for 0.17.0. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.