Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/145
+1 looks good
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/145
Bump - anyone? Bueller?
@nickwallen - those changes you requested have been for a bit.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/145
I was thinking `metron_elasticsearch`. That way, if we have other ES
related code we need for Metron, it also works in the same role.
I have some changes I can make in
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/145
So, specifically, you'd like to see elasticsearch_templates ->
metron_elasticsearch_templates?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/145
I like the METRON-211 style: `metron_kafka`, `metron_hbase`,
`metron_elasticsearch`. This also more closely matches the existing
`metron_streaming` role
---
If your project is set up
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/145
What's your concern about starting Elasticsearch? The service module should
support the environment. In the initial deploy path, ES will be installed but
stopped when we execute this.
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/145
I'm wondering where the best place is to store things like Elasticsearch
template definitions. Ultimately, creating an effective Elasticsearch template
is an important part of creating
