-
Notifications
You must be signed in to change notification settings - Fork 795
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ElasticSearch 2.0 #8
Comments
That's a good question... I haven't had a chance to use 2.0 yet, because I've been waiting to see how support lands in the Chef cookbook. Is the break from an element removal or something getting renamed / moved? |
The break is because NodeStatsOSResponse.LoadAvg is a float64 rather than []float64. |
I looks like LoadAvg is never used so it should be fine to delete that and be compatible with both 1.x and 2.x. wdyt? |
I apologize for leaving this hanging. Let me pull down ES 2.x right now and take a look. |
* Addresses #8 * Update README to note changes in ES 2.0 * Add stats for thread pool
I've pointed this at a busy cluster and the metrics endpoint looks great. I've not checked the accuracy of the data -- I'll follow up with a different issue if there's anything unexpected for 2.0. Thanks! |
There are quite a few changes in ElasticSearch 2.0, one of which breaks the JSON deserialization.
What kind of plan would you take for supporting 1.x/2.x?
The text was updated successfully, but these errors were encountered: