[
https://issues.apache.org/jira/browse/AMBARI-15609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249043#comment-15249043
]
Juanjo Marron commented on AMBARI-15609:
----------------------------------------
mvn clean test -DskipSurefireTests
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Main ....................................... SUCCESS [52.199s]
[INFO] Apache Ambari Project POM ......................... SUCCESS [1.008s]
[INFO] Ambari Web ........................................ SUCCESS [1:55.020s]
[INFO] Ambari Views ...................................... SUCCESS [10.201s]
[INFO] Ambari Admin View ................................. SUCCESS [28.427s]
[INFO] ambari-metrics .................................... SUCCESS [1.984s]
[INFO] Ambari Metrics Common ............................. SUCCESS [2.614s]
[INFO] Ambari Metrics Hadoop Sink ........................ SUCCESS [3.273s]
[INFO] Ambari Metrics Flume Sink ......................... SUCCESS [1.014s]
[INFO] Ambari Metrics Kafka Sink ......................... SUCCESS [1.121s]
[INFO] Ambari Metrics Storm Sink ......................... SUCCESS [3.095s]
[INFO] Ambari Metrics Collector .......................... SUCCESS [44.049s]
[INFO] Ambari Metrics Monitor ............................ SUCCESS [4.723s]
[INFO] Ambari Metrics Grafana ............................ SUCCESS [25.620s]
[INFO] Ambari Metrics Assembly ........................... SUCCESS [46.641s]
[INFO] Ambari Server ..................................... SUCCESS [2:37.916s]
[INFO] Ambari Functional Tests ........................... SUCCESS [2.405s]
[INFO] Ambari Agent ...................................... SUCCESS [17.269s]
[INFO] Ambari Client ..................................... SUCCESS [0.428s]
[INFO] Ambari Python Client .............................. SUCCESS [1.825s]
[INFO] Ambari Groovy Client .............................. SUCCESS [22.088s]
[INFO] Ambari Shell ...................................... SUCCESS [0.389s]
[INFO] Ambari Python Shell ............................... SUCCESS [0.116s]
[INFO] Ambari Groovy Shell ............................... SUCCESS [13.794s]
[INFO] ambari-logsearch .................................. SUCCESS [2.336s]
[INFO] Ambari Logsearch Portal ........................... SUCCESS [8.900s]
[INFO] Ambari Logsearch Log Feeder ....................... SUCCESS [2.282s]
[INFO] Ambari Logsearch Appender ......................... SUCCESS [0.502s]
[INFO] Ambari Logsearch Assembly ......................... SUCCESS [0.425s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 9:34.234s
[INFO] Finished at: Tue Apr 19 17:05:47 PDT 2016
[INFO] Final Memory: 124M/560M
> Refactor get_stack_to_component() method
> ----------------------------------------
>
> Key: AMBARI-15609
> URL: https://issues.apache.org/jira/browse/AMBARI-15609
> Project: Ambari
> Issue Type: Technical task
> Components: ambari-agent, ambari-server
> Affects Versions: 2.1.0, 2.2.0
> Reporter: Juanjo Marron
> Assignee: Juanjo Marron
> Priority: Minor
> Fix For: 2.4.0
>
> Attachments: AMBARI-15609.patch
>
>
> The original intention of the get_stack_to_component function was to have a
> dictionary where the key was the stack name.
> At service level we always return the same key no matter what, then we should
> just return the string with the component name and no need to check
> params.stack_name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
