-
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
DocValuesField \"value\" is too large, must be <= 32766 #595
Comments
Hm, interesting, you've got a huge index definition, so it can't be stored in |
@pyromaniac Yes, I have nearly 400 models and over 3000 fields. It looks like disabling doc_values means that I can't sort or aggregate on fields. I'm not sure what the Chewy stash is; is sorting or aggregate on the |
I added
I define types roughly like this:
I have one model that has a If I change the |
Hey, did you find anything else? I'm going to try the binary type out |
Hey, can you try #602 ? It supposed to fix your issues |
@pyromaniac Thank you, but it didn't work. I applied your patch to a branch off v0.10.1 and updated my Gemfile with:
I ran
|
Wow, this is also unexpected. So, there is no other way to do it but a binary field. Thanks. |
Hm, btw, why are you defining everything inside a single index? This is not the best idea, I would split indexes per model as well. And then there will be no problems for you. |
@pyromaniac I'm not sure if it's the best way to do it, but I have a website feature that searches "all data" - so I want to search all models at once. Each model has an
Or I can limit it to a particular model:
|
First of all, you can use |
Interesting, ok, I'll look into refactoring. One issue is that right now within my |
I'm pretty sure you can. Just use |
Hello, I just achieved the same issue with next index
Error happens on
I didn't receive that error until I updated to latest version. Any ideas why it may happen and how I can avoid it? Thanks |
I found note https://www.elastic.co/guide/en/elasticsearch/reference/current/nested.html#_limiting_the_number_of_literal_nested_literal_fields As I got from the code it's used just for comparing if current specification changed from last indexed version, can't we just use plain string or md5 hash of this specification for this comparison? |
Hey, it is a good idea about MD5, but I've got plans for this object proper comparison. Can you try to use the latest master? The limit should be increased there. |
right now I'm using the latest master but still got this error |
Which error btw? |
|
Oh, right, okay, thanks. Seems like the only way is to use |
ok thanks |
Looks like @kevgrig problem is solved by the newest version. Can we close this issue? |
I'm using chewy |
@mattzollinhofer Yep, issue has already been closed since last November, although it's great that now I can just use the latest version to work around the issue instead of a branch, thanks! Ultimately, I need to re-architect my models for ES6 based on a comment above, which I've been avoiding because things work for now... |
Hi, I'm calling
reset!
on my index and it's throwing the following exception. Chewy is not providing details on how to investigate this:Nothing in my models with "value":
Index definition: https://github.com/myplaceonline/myplaceonline_rails/blob/master/app/lib/user_index.rb
The text was updated successfully, but these errors were encountered: