You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Few days ago I asked about error because of incompatibility nest 1.0 with elsticsearch 0.90. I searched a way to get NoMatchSize param(don't support in NEST 0.12) and found some old issues #428 & #443 that contains some words about NEST 0.90. But I don't found it in tags or branches. Think that it can help me)
Sorry for obtrusiveness.
I can't solve the problem with returning a part of big field to optimize query speed without no_match_sizes or changing structure of db using nest 0.12. Search is fast, but braking is applied when loading results.
The text was updated successfully, but these errors were encountered:
NEST 0.90 was suppose to be an intermediary version between 0.12 and 1.0 but we opted to not release it and go for a clean 1.0 release.
We opted to only fully support Elasticsearch 1.0 and onwards since the 0.90 EOL is coming up fast.
PS: you are not being obtrusive at all! Feel free to open as many issues as you want I am sure you are not the only one who runs into this stuff. This issue will come up for someone's google search in the future and they'll be happy you were 'obtrusive' 👍
Hi! Few days ago I asked about error because of incompatibility nest 1.0 with elsticsearch 0.90. I searched a way to get NoMatchSize param(don't support in NEST 0.12) and found some old issues #428 & #443 that contains some words about NEST 0.90. But I don't found it in tags or branches. Think that it can help me)
Sorry for obtrusiveness.
I can't solve the problem with returning a part of big field to optimize query speed without no_match_sizes or changing structure of db using nest 0.12. Search is fast, but braking is applied when loading results.
The text was updated successfully, but these errors were encountered: