[
https://issues.apache.org/jira/browse/METRON-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572304#comment-16572304
]
ASF GitHub Bot commented on METRON-1695:
----------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/1132
I don't see any good reason to put off making pcap it's own Ambari
component. Having to restart the parsers component (which is unrelated to
pcap) to propagate pcap changes is a deal breaker for me.
Had this been submitted against the pcap feature branch I would be fine
with it as an incremental change but I don't feel like this puts master in a
good state and I definitely would not want it in a release. Why not just do it
here?
> Expose pcap properties through Ambari
> -------------------------------------
>
> Key: METRON-1695
> URL: https://issues.apache.org/jira/browse/METRON-1695
> Project: Metron
> Issue Type: Bug
> Reporter: Anand Subramanian
> Assignee: Anand Subramanian
> Priority: Major
>
> Currently, the $METRON_HOME/config/pcap.properties file is hardcoded with the
> defaults. One has to hand edit the file before deploying the PCAP topology.
> These properties should be configurable via Ambari.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
