-
-
Notifications
You must be signed in to change notification settings - Fork 515
Upgrade to Elasticsearch 5.x #145
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
Comments
When plans to support Elasticsearch 2.x |
We will be skipping 2.x completely and going straight to 5.x by using external reindexing support built into 5.x. We are starting work on this process this week so we can be ready for the 5.x release and reap the many rewards of 2.x+5.x (80% faster indexing, update by query and much more). |
Support Elasticsearch 5.x, also supports Elasticsearch 2.x? |
We will be skipping 2.x and going straight to 5.x via external reindexing. |
We have an /elastic5 branch that we are working out of :) |
elastic5 release ,This release introduces a number of breaking changes. https://www.elastic.co/blog/elasticsearch-5-0-0-released |
Yep, a whole lot of them, we just got foundatio.repositories completely upgraded and are working on exceptionless, we almost have the mappings done but we are blocked until they release a NEST-5.0-rc2 client |
https://www.nuget.org/packages/NEST/5.0.0-rc2 NEST-5.0-rc2 release |
We need to work on reindexing next (dev will be upgraded to elastic 5 today or tomorrow).. The reindex will need to have an ingest pipeline which choices the right daily index. |
App is looking good. Tons of hard work paying off. :) |
I have exceptionless up and running on elastic 5 (https://dev-app.exceptionless.io/) Feel free to play around with it. I only have it running on a single node (haven't even optimized that node) I just did find an issue where I wasn't able to invite users / get users list for an org, will look into that very soon. Other than that I'm aware of no issues but I'm sure there probably are |
We've deployed this into production, we'll create a release soon once we have more data |
We need to reindex all data and update the client for Elasticsearch 2.0 as things have been deprecated. We should compile a list of these as well as look into performance gains that could be achieved via a reindex.
Performance gain:
The text was updated successfully, but these errors were encountered: