Return-Path: X-Original-To: apmail-oodt-commits-archive@www.apache.org Delivered-To: apmail-oodt-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6455F10691 for ; Mon, 10 Jun 2013 20:06:20 +0000 (UTC) Received: (qmail 64066 invoked by uid 500); 10 Jun 2013 20:06:20 -0000 Delivered-To: apmail-oodt-commits-archive@oodt.apache.org Received: (qmail 64048 invoked by uid 500); 10 Jun 2013 20:06:20 -0000 Mailing-List: contact commits-help@oodt.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@oodt.apache.org Delivered-To: mailing list commits@oodt.apache.org Received: (qmail 64040 invoked by uid 99); 10 Jun 2013 20:06:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Jun 2013 20:06:20 +0000 Date: Mon, 10 Jun 2013 20:06:20 +0000 (UTC) From: "Rajith Siriwardana (JIRA)" To: commits@oodt.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (OODT-618) Implement ganglia XML parser MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OODT-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679836#comment-13679836 ] Rajith Siriwardana edited comment on OODT-618 at 6/10/13 8:04 PM: ------------------------------------------------------------------ Hey Chris, I've attached a patch "oodt 618_Implement ganglia XML parser_v3.patch" with the 2 and 3 suggestions. since with the SAX parser I've only coded tag comparisons by extending the default handler, there is nothing to be added to the XMLUtils from parser. but as DOM parser we can add getting SAX parser instance like methods to XMLUtils for generalization. Next thing you highlighted was using o.a.oodt.cas.resource.struct.ResourceNode for ganglia HOST structure. Since ganglia Host struct contains more ganglia specific attributes, I think its better to keep away from o.a.oodt.cas.resource.struct.ResourceNode. example NodeId like atribs are not in ganglia domain. WDYT? Cheers, was (Author: rajiths): Hey Chris, I've attached a patch with the 2 and 3 suggestions. since with the SAX parser I've only coded tag comparisons by extending the default handler, there is nothing to be added to the XMLUtils from parser. but as DOM parser we can add getting SAX parser instance like methods to XMLUtils for generalization. Next thing you highlighted was using o.a.oodt.cas.resource.struct.ResourceNode for ganglia HOST structure. Since ganglia Host struct contains more ganglia specific attributes, I think its better to keep away from o.a.oodt.cas.resource.struct.ResourceNode. example NodeId like atribs are not in ganglia domain. WDYT? Cheers, > Implement ganglia XML parser > ---------------------------- > > Key: OODT-618 > URL: https://issues.apache.org/jira/browse/OODT-618 > Project: OODT > Issue Type: Sub-task > Components: resource manager > Reporter: Rajith Siriwardana > Assignee: Rajith Siriwardana > Fix For: 0.6 > > Attachments: OODT-618 Implement ganglia XML parser.patch, oodt 618_Implement ganglia XML parser_v3.patch > > > This will consists with Ganglia XML reader and ganglia metric builder. The received XML will be parsed and it will creates a node which is a tree structure and also a java list consisting the stats of the Resource Nodes by holding ganglia metrics. which can be queried as preferred. -- 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