[
https://issues.apache.org/jira/browse/METRON-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16573242#comment-16573242
]
ASF GitHub Bot commented on METRON-1695:
----------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/1132
If you want to do the work in a separate PR (METRON-1709) then that's fine.
As long as they are tested and committed together that works for me. If it
were me, I would just do the work in this PR and save the trouble of managing
two different PRs. We have several different components already that you can
use as a template. I don't think this is that much work.
Since this was developed against master I wouldn't switch to the feature
branch.
> 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)
