[
https://issues.apache.org/jira/browse/METRON-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637343#comment-16637343
]
ASF GitHub Bot commented on METRON-1695:
----------------------------------------
Github user anandsubbu commented on the issue:
https://github.com/apache/metron/pull/1207
@MohanDV , as a part of my commit, I have moved all the UI related elements
from REST to the PCAP config tab.
In my understanding, the following parameters are not directly related to
the PCAP core service, but are functionally related to REST (used by the PCAP
query panel UI):
* pdml.script.path
* base.path
* base.interim.result.path
* final.output.path
* page.size
* yarn.queue
* finalizer.threadpool.size
For this reason, I did not move these properties out of the
rest_application.yml.
> @MohanDV Changing a REST Setting triggers Ambari to Restart PCAP Topology
With my current changes, modifying any config setting in the PCAP tab will
require restarting both Metron PCAP and Metron REST services--which is
necessary since user can change a PCAP-service related property or a PCAP-REST
related property (or both). The converse, which you noted, i.e. changing any
REST config does not require restarting the PCAP topology. Here's a screenshot
after making changes to REST config...
> 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)
