You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2017/04/27 14:56:04 UTC
[jira] [Commented] (AMBARI-20869) Changes to events format
[ https://issues.apache.org/jira/browse/AMBARI-20869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986766#comment-15986766 ]
Hadoop QA commented on AMBARI-20869:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12865385/AMBARI-20869.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11511//console
This message is automatically generated.
> Changes to events format
> ------------------------
>
> Key: AMBARI-20869
> URL: https://issues.apache.org/jira/browse/AMBARI-20869
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-20869.patch, AMBARI-20869.patch, AMBARI-20869.patch, AMBARI-20869.patch
>
>
> Changes we discussed with Myroslav Papyrkovskyy to format data in more suitable
> for server way.
> * use cluster id instead of name
> * remove some dictionary keys in events to make handing them simpler
> * don't use component name as key in topology dictionary to be ready for multiInstances work.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)