I assume you're taking about METRON-939. The upgrade is not a huge change, and
unlikely to touch any of the bulk writing pieces. The main thing outstanding on
the PR is log4j dependency conflicts from the new ES client.
There's no work in that PR to do anything around mpack based install either so
that's a fair chunk of outstanding busy work and significant testing.
> On 17 Jul 2017, at 12:39, Ali Nazemian <alinazem...@gmail.com> wrote:
> Hi all,
> I've heard there is a plan to upgrade Elasticsearch from 2.x to 5.x
> regarding Metron and Ambari mpack. I was wondering when that will happen.
> Is there any part in Metron Elasticsearch indexing that will be impacted by
> this upgrade? Like any change from the way of bulk-indexing?