[
https://issues.apache.org/jira/browse/METRON-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572747#comment-16572747
]
ASF GitHub Bot commented on METRON-1695:
----------------------------------------
Github user anandsubbu commented on the issue:
https://github.com/apache/metron/pull/1132
This PR lays the foundation for exposing the properties to begin with. My
thought was that it reduces one error prone manual step of hand-editing the
`pcap.properties` file. I agree with your point about how users might be
concerned about restarting all parsers after modifying PCAP config.
I did not create this earlier under the feature branch since this was not
related specifically to the PCAP query panel, it was a more generic change.
I am fine to move this under the feature branch or I could wait until the
fix for METRON-1709 (making the PCAP service its own) is available and then
submit a fresh PR. Let me know which one works better.
> 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)
