[
https://issues.apache.org/jira/browse/METRON-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16565683#comment-16565683
]
ASF GitHub Bot commented on METRON-1695:
----------------------------------------
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1132
I think I'm ok with this as a first step. Please document the lifecycle for
how pcap.properties is updated in the README. It should be clear to users that
they will need to restart parsers for the changes to take effect after the
initial install is performed. Can you confirm, is that the way the properties
are/will be deployed with this PR @anandsubbu?
https://github.com/apache/metron/pull/1134 should be included in the
refactoring once we make PCAP a proper component.
> 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)
