GitHub user hvivani opened a pull request:

https://github.com/apache/bigtop/pull/138

BIGTOP-2517: Elasticsearch 1.6 for Bigtop

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/hvivani/bigtop BIGTOP-2517

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/bigtop/pull/138.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #138

commit cd33e95b2582b0aaca920622073611f9b79edd65
Author: Hernan Vivani <hernan@vivani.com.ar>
Date: 2016-08-11T14:59:37Z

BIGTOP-2517: Elasticsearch 1.6 for Bigtop

https://github.com/apache/bigtop/pull/138.patch

The patch and blog looks really great. Thanks Hernan Vivani.
While what you provided are good. I think at this point we does not have enough knowledge in Elasticsearch yet.
If you're ok to be a maintainer of this component.
Then we can find a way to work with you and get the patch in.
How do you think?

Hello Evans,
Yes, I'll be more than glad to help here. Do you want me to update the maintainers file with my information ?

Created https://github.com/apache/bigtop/pull/183 to add hernan vivani as maintainer for elasticsearch.

Hernan Vivani that would be awesome!
We can add you into maintainer list first, and then get back to the business of ES inclusion.
From what I can see, version 1.6 is quite outdated. ES itself seems to have a huge bump of version just like firefox.
Any chance to bump the version up-to-date while rebasing the patch?

OTOH, please create another JIRA to host your PR-183.
That way every changes has been tracked.
Thanks.

Hi Evans,
As per your comments, I've created https://issues.apache.org/jira/browse/BIGTOP-2694 for the maintainer request, and closed PR-183.
I think we can add ES 1.6 as initial version and will start the work to create an ES 2.x version and then ES 5.x version.
Thank you guys for the opportunity!

Actually I'm very unfamiliar with ES, but it seems that 1.6 is quite old (released 09 June 2015).
I think we'd be better to include newest, or at least newer/popular version of ES.
FYI, we're close to the release of Bigtop 1.2, hence inclusion of a new component with old version looks pretty strange.
Are you ok to bump the version up?

Hello Evans,
There are many structural changes between 1.x, 2.x and 5.x. Depending on the prod environment and the cost of migration, we have still users running on 1.x, others working on 2.x and finally new ones (or the ones that migrated all the structure) to ES 5.x.
Yes, I'll work to bump the version up. Will create another Jira for that version.

Hernan Vivani I personally would love to see a newer version of ES being included in Bigtop. That's much more reasonable for an addition of new component. Sorry for being late on paying attention to this JIRA. Please ping me directly if you get any progress on this.

Hello Evans,
Sorry for the delay here.
I started the work on it but got sidetracked with other issues and I couldn't advance to much yet. The structure is pretty different so I'm working recreating the SPEC and will need to perform some proper tests to see if everything works properly.
I'll keep you posted.

Hernan Vivani anything we can help?