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

ASF GitHub Bot commented on METRON-1599:
----------------------------------------

Github user merrimanr commented on a diff in the pull request:

    https://github.com/apache/metron/pull/1047#discussion_r194168714
  
    --- Diff: 
metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/package/scripts/alerts_ui_master.py
 ---
    @@ -40,10 +41,9 @@ def install(self, env):
             self.install_packages(env)
     
         def configure(self, env, upgrade_type=None, config_dir=None):
    -        print 'configure alerts_ui'
             from params import params
             env.set_params(params)
    -
    +        metron_service.refresh_configs(params)
    --- End diff --
    
    If we move the property to metron-rest-env then I'm not sure this is 
necessary.  


> Allow user to define global property 'source.type.field' in Ambari 
> -------------------------------------------------------------------
>
>                 Key: METRON-1599
>                 URL: https://issues.apache.org/jira/browse/METRON-1599
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Nick Allen
>            Assignee: Nick Allen
>            Priority: Major
>
> The user can specify the name of the message field containing the source type 
> in the global configuration.  This is used by the Alerts UI.
> Currently this necessitates a user using the CLI to add the field. This 
> property should be exposed to the user via Ambari.  The user should be able 
> to define this property directly in Ambari.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to