[
https://issues.apache.org/jira/browse/METRON-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876539#comment-15876539
]
ASF GitHub Bot commented on METRON-646:
---------------------------------------
Github user kylerichardson commented on the issue:
https://github.com/apache/incubator-metron/pull/441
bump... I read back through the discuss thread from the dev list and we
didn't land on any specifics. There seems to be general agreement that
metron-docker:
- fulfills a current need/desire for targeted development and testing (e.g.
parsers)
- could be used to make integration testing quicker and easier (requires
exploration)
How do we want to move this forward? I have this and a follow-on PR ready
to go for adding HDFS into metron-docker.
> Add index templates to metron-docker
> ------------------------------------
>
> Key: METRON-646
> URL: https://issues.apache.org/jira/browse/METRON-646
> Project: Metron
> Issue Type: Improvement
> Reporter: Kyle Richardson
> Assignee: Kyle Richardson
> Priority: Minor
>
> Customize the elasticsearch docker image:
> # to have the elasticsearch-head plugin installed as part of the image build
> # copy the es_templates into the image so they are available
> # deploy the templates on container start
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
