[
https://issues.apache.org/jira/browse/METRON-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840130#comment-15840130
]
ASF GitHub Bot commented on METRON-641:
---------------------------------------
Github user mattf-horton commented on the issue:
https://github.com/apache/incubator-metron/pull/425
Thanks, @dlyle65535 . Couple more comments:
- Also included is the small change proposed in METRON-641 to use {0}
instead of {} in python format strings in kibana_master.py. It shouldn't be
necessary for Python 2.7, but these are the only usages of the 2.7 behavior,
and there's no harm in making it also work with Python 2.6.
- The biggest deficiency, as far as I'm concerned, is the need to use a
different, sparser template for a single-node "elasticsearch.master.yaml.j2".
Presumably only one or two of the removed parameters are actually a problem,
and presumably even those don't really have to be removed but simply need a
different value. But it looked like a big job to figure out. Perhaps someone
more familiar with Elasticsearch would be able to solve it.
> Fix Kibana install file
> -----------------------
>
> Key: METRON-641
> URL: https://issues.apache.org/jira/browse/METRON-641
> Project: Metron
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Dima Kovalyov
> Priority: Minor
>
> Kibana installed as part of Metron mpack winthin Ambari will fail during
> start with following error:
> {code}
> ValueError: zero length field name in format
> {code}
> We can fix it with:
> {code}
> sed -i 's@{}/kibana@{0}/kibana@g'
> /incubator-metron/metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/KIBANA/4.5.1/package/scripts/kibana_master.py
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
