metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nickwallen <>
Subject [GitHub] metron pull request #613: METRON-990: Clean up and organize flux properties
Date Wed, 21 Jun 2017 15:55:36 GMT
Github user nickwallen commented on a diff in the pull request:
    --- Diff: metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/configuration/metron-env.xml
    @@ -253,69 +253,295 @@
    -        <name>global-json</name>
    -        <display-name>global.json template</display-name>
    -        <description>This is the jinja template for global.json file</description>
    -        <value>
    -"es.clustername": "{{ es_cluster_name }}",
    -"es.ip": "{{ es_url }}",
    -"": "yyyy.MM.dd.HH",
    -"parser.error.topic": "indexing"
    -        </value>
    +        <name>es_date_format</name>
    +        <description>Elasticsearch Date Format</description>
    +        <value>yyyy.MM.dd.HH</value>
    +        <display-name>Elasticsearch Date Format</display-name>
    +    </property>
    +    <property>
    +        <name>parser_error_topic</name>
    +        <description>Parser Error Topic</description>
    +        <value>indexing</value>
    +        <display-name>Parser Error Topic</display-name>
    +    </property>
    +    <property>
    +        <name>enrichment_workers</name>
    --- End diff --
    After deploying in Full Dev, I went into Ambari and changed some Enrichment properties
like "Enrichment Workers".  After saving the changes, Ambari indicated that I needed to restart
all of the Metron-related components.  Even unrelated components like the Metron Management
UI.  It only really needed to restart the Enrichment topology. 
    I am not sure what logic controls that.  Is that something controlled in this PR?  Or
is that external to these changes?

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message