You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Michael Miklavcic (JIRA)" <ji...@apache.org> on 2016/08/01 16:05:20 UTC

[jira] [Updated] (METRON-356) Enable topology classpath to be updated via configuration

     [ https://issues.apache.org/jira/browse/METRON-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Miklavcic updated METRON-356:
-------------------------------------
    Description: The current approach for including *-site.xml files with the Storm topologies is to manually update the topology jar files with the necessary configs. With this current technique for setting classpath, ongoing changes to the cluster config are not reflected when updates are made via Ambari. This jira seeks to remedy that problem.  (was: The current approach for including *-site.xml files with the Storm topologies is to manually update the topology jar files with the necessary configs. With this current technique for setting classpath, ongoing changes to the cluster config are not reflected when updates are made via Ambari. This jira seeks to remedy that problem by coming up.)

> Enable topology classpath to be updated via configuration
> ---------------------------------------------------------
>
>                 Key: METRON-356
>                 URL: https://issues.apache.org/jira/browse/METRON-356
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Michael Miklavcic
>            Assignee: Michael Miklavcic
>
> The current approach for including *-site.xml files with the Storm topologies is to manually update the topology jar files with the necessary configs. With this current technique for setting classpath, ongoing changes to the cluster config are not reflected when updates are made via Ambari. This jira seeks to remedy that problem.



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