[
https://issues.apache.org/jira/browse/METRON-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572490#comment-16572490
]
ASF GitHub Bot commented on METRON-1695:
----------------------------------------
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1132
@anandsubbu, I hate to give you whiplash, but @merrimanr may have a point
here. There benefit of exposing the pcap properties via Ambari is lessened by
now requiring the user to do 3 things instead of 2 to get the properties set
for Pcap.
**Old**
1. Update properties
2. Restart pcap from command line
**New**
1. Update properties
2. Restart parsers to deploy the properties (users may not like this
requirement)
3. Restart pcap from command line
The work is by no means throw away in its current form, but if we're going
to do this it's probably worth going the whole way.
> 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)
