ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Masahiro Tanaka (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-17614) Clean up import * for AMBARI_METRICS services
Date Thu, 14 Jul 2016 17:13:20 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-17614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15377295#comment-15377295
] 

Masahiro Tanaka commented on AMBARI-17614:
------------------------------------------

Thanks [~sumitmohanty] and [~avijayan]!

> Clean up import * for AMBARI_METRICS services
> ---------------------------------------------
>
>                 Key: AMBARI-17614
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17614
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-metrics
>    Affects Versions: 2.4.0
>            Reporter: Masahiro Tanaka
>            Assignee: Masahiro Tanaka
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17614.1.patch, AMBARI-17614.patch
>
>
> {{ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/status.py}}
and {{ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_monitor.py}}
> uses {{from resource_management import *}}. It increases code tracking difficulty.
> I think this is related to AMBARI-16101



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message