+1 I agree with Otto's idea. It makes a lot of sense for Elasticsearch and Kibana to live in a separate Mpack.
This provides us a path forward to support additional indexers like Solr. We should also not force our users to install an external component (like Elasticsearch) using the Mpack. There are just too many installation configurations for us to reasonably support; especially on larger installations. Supporting the Elasticsearch MPack is a project unto itself. That being said, the functionality will still be there for those that want to use it. On Fri, Feb 16, 2018 at 4:10 PM, Michael Miklavcic < michael.miklav...@gmail.com> wrote: > This came up earlier when discussing work around the ES upgrade: > https://lists.apache.org/thread.html/66280bc061afbba2c353221c3c05fd > 74b247b970921c009c29edc815@%3Cdev.metron.apache.org%3E > https://lists.apache.org/thread.html/8ec83b6a3ef39057c9466ff72a2f63 > c9308452f1ebc1804e67cb495b@%3Cdev.metron.apache.org%3E > > Looks like Otto made this suggestion and Kyle is on board. I was originally > opposed to this because it did not seem worth the effort to support 2 > separate MPacks. However, now that we are working on the Solr upgrade, it > seems like an appropriate solution for enabling us to make the indexing > piece pluggable. I propose that we commence with this solution. > > Cheers, > Mike >
