From hdfs-issues-return-31501-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org Mon Jan 2 09:41:14 2012 Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 54771B95E for ; Mon, 2 Jan 2012 09:41:14 +0000 (UTC) Received: (qmail 22435 invoked by uid 500); 2 Jan 2012 09:41:13 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 22133 invoked by uid 500); 2 Jan 2012 09:40:59 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 22115 invoked by uid 99); 2 Jan 2012 09:40:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jan 2012 09:40:55 +0000 X-ASF-Spam-Status: No, hits=-2001.6 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jan 2012 09:40:52 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id BEB1B1345A7 for ; Mon, 2 Jan 2012 09:40:30 +0000 (UTC) Date: Mon, 2 Jan 2012 09:40:30 +0000 (UTC) From: "Uma Maheswara Rao G (Commented) (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <702685246.57536.1325497230782.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HDFS-402) Display the server version in dfsadmin -report MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HDFS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178330#comment-13178330 ] Uma Maheswara Rao G commented on HDFS-402: ------------------------------------------ Hey Harsh, This should not be the finalized version of the patch. Did you check my comments above? Patch is just another way for the Dhruba's suggestion. Since there was a discussion before this, i just updated as per their discussion and asked for the remaining clarification on my above comment. Thanks for your comments. {quote} If we really need to get the version info from NN, then we may need to expose some api in Filesystem to get into DFSAdmin, else above patch can satisfy the needs. {quote} Thanks Uma > Display the server version in dfsadmin -report > ---------------------------------------------- > > Key: HDFS-402 > URL: https://issues.apache.org/jira/browse/HDFS-402 > Project: Hadoop HDFS > Issue Type: Wish > Reporter: Jakob Homan > Priority: Minor > Labels: newbie > Attachments: HDFS-402.patch > > > As part of HADOOP-5094, it was requested to include the server version in the dfsadmin -report, to avoid the need to screen scrape to get this information: > bq. Please do provide the server version, so there is a quick and non-taxing way of determine what is the current running version on the namenode. > Currently there is nothing in the dfs client protocol to query this information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira