-
Notifications
You must be signed in to change notification settings - Fork 368
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 6.0.0 support? #609
Comments
Curious about it too, we search across multiple types with Chewy so I suspect https://www.elastic.co/guide/en/elasticsearch/reference/6.0/removal-of-types.html will be a tricky one to handle. We'll do some testing and report. |
Will try to find a time for it the next week. But I assume it should work. Did you try it? |
It doesn't work properly with 6.0. A couple of issues I could identify. First. is that 6.0 no longer recognizes the field type "string", which is chewy's default type. You have to change them all to "text".
In addition, you're no longer able to add multiple models to one index. Here's an example of the error message you get when running
I also had to be sure to set |
The main problem, as it seems to me, is the removal of multitype support https://www.elastic.co/guide/en/elasticsearch/reference/6.0/removal-of-types.html. Chewy's multiple types logic should be rewritten to use custom type field within the single mapping to use multiple index sources for the single index. |
It is not actually removed, it is just deprecated, so the only thing we need for users that will decide to use a single-type setup is some multi-index query interface. And maybe an ability to define mapping on index directly, without defining a type |
+1 |
Elasticsearch::Transport::Transport::Errors::BadRequest: [400] {"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"No handler for type [string] declared on field [type_name]"}],"type":"mapper_parsing_exception","reason":"Failed to parse mapping [journal]: No handler for type [string] declared on field [type_name]","caused_by":{"type":"mapper_parsing_exception","reason":"No handler for type [string] declared on field [type_name]"}},"status":400} getting this error on "rake chewy:reset" ... i have changed default type from string to text still getting this error... |
@vishalsingh123 I have the same problem, when I run rake chewy:reset, I get same error message, but index is always created. If you take a look on message from elastic log below, it says: deleting index, but when I run curl 'localhost:9200/_cat/indices?v' I see, that actually it's created (with different name cards_123123123). Here is log from elastic: [2018-01-10T11:05:02,206][INFO ][o.e.c.m.MetaDataCreateIndexService] [1_mxHwD] [cards_1515578702175] creating index, cause [api], templates [], shards [5]/[1], mappings [card] Actually the error occurs while trying to use rake:reset Hope it helps. |
It looks like some work has started to support ES6 here #622 I also just added a bit of information related to @pyromaniac you mentioned the only issue being that multiple types is deprecated, not removed. This is partially correct, it looks like indexes created in ES5 with multiple types will continue to work in ES6, but you cannot create new multiple type indexes in ES6. This makes getting started with this gem and ES6 challenging since the |
Any update on ES6 support? |
Sorry, but nothing much yet, still have a lot of stuff happening besides it. But I definitely will get back here eventually and rather sooner than later. |
Any new updates on ES6 support? |
@breisig with some of the patches that were merged a few months ago it has been working well for me. I’m not using multi-type indexes at all though so not sure if you might run into issues if you are using those. |
@jduff just wondering if you are using any joins to define relations. Currently am using the parent child and trying to find a work around so we can upgrade elasticsearch and still use Chewy. |
I don’t have any complicated joins in the data being indexed, but I do include a bunch of associated models and have data from them in the index. |
I also would like to know if there's an ETA on ES6 support. I have one multi-type index which is preventing me from upgrading. |
We're now 7 months away from the official EOL date for Elasticsearch 5.6.x @pyromaniac Is there an ETA on this? |
Well, I'm trying hard to find a time for this atm. So it should be kinda soonish. |
Thank you for the response! The work you do is very well appreciated. I look forward to seeing the changes! |
It sounds like some people are successfully using the current version of chewy with ES6. But this thread has gotten a little confusing. Are there still known outstanding issues for ES 6? @pyromaniac do you think you could create issue(s) with a label of “ES 6” and if there’s any I can take a look at I could try to help? I’m not on ES 6 yet, but will be moving there soon so would like to help if I can. |
@mattzollinhofer well, yeah, it might be a good idea. I just need to stop procrastinating and get to it. Also, multi-index queries support just landed in master as a next step of ES6 support |
I pinned my Gemfile to master on Github - not sure if this is expected, but when running
|
Not sure if its there or I can't find it, but is there a way to associate multiple types with an index yet? |
I'm still having the issue about multiple indexes ( ES 5 has now reached its EOL (https://www.elastic.co/fr/support/eol), any update on this? |
Is chewy abandoned? It's ok that it is, we just need some clear warning on the homepage. |
@pyromaniac first of all, thanks for the work you did, I really appreciate it. I have a question about multi-type indexes. As it stated in ES6 docs, it's still possible to use multiple types as one type, using |
Hey @marselmustafin 👋 ! |
@rubenfonseca We've just released chewy 5.2.0 with a couple of fixes and added support for the ruby 3.0, and working to bring in ES6 support, and then - ES7. |
@rabotyaga That is great news. Do we have any timeline around ES6 support? Even if it is an estimate that would be great, thanks for the all work! |
@aabhushan Strictly speaking, nothing stops you from using chewy 5.2 with ES6. You just have to remove any multi-type mappings and make sure you don't use any of the deprecated ES5 features. |
I can confirm current Chewy works fine with ES 6.x. (I use 6.4.1 in production.) |
That is great news, @rabotyaga @abartov, upgrading ES to 6 and wanted to make sure we won't face any issues. Thanks!! |
Now that Elasticearch 6.0.0 has been released [ https://www.elastic.co/blog/elasticsearch-6-0-0-released ], Is there support for chewy to work with 6.0.0?
The text was updated successfully, but these errors were encountered: