-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Fields not appearing as searchable, aggregatable in 5.3.1 on upgrade from 2.3.3 and 5.2.2 #11377
Comments
Setting fielddata to true will show the fields in Kibana drop downs. It seems this change was made to prevent heavy system load from happening. If you use |
The |
For fields=* it gives an exception:
for one field i.e messagetype:
Field with geo_point type is the only field which is appearing as aggregatable and searchable, on querying field_stats for that as well I get exception:
Stacktrace from elasticsearch for the same:
|
Thanks for the extra info @vineet01. This is definitely the same bug as #11379 which is ultimately caused by elastic/elasticsearch#24275. I don't have a workaround yet, I'll try to come up with something and post it to #11379. Going to close this ticket as a dupe. |
Example mapping in ES 2.3.3 for a field:
On upgrade to 5.2.2/5.3.1, mapping becomes like:
Now with this mapping, in 5.2.2 the field is still aggregatable, however, in 5.3.1 it is not. Same for fields with "long" type as well.
I am also not sure about the reason for above mapping change and addition of fielddata:false. Not sure if that might be causing the trouble. (https://discuss.elastic.co/t/mapping-change-on-upgrade-to-5-2-2/82622)
In field_stats I am able to see that it is marked as aggregatable:
But Kibana is not showing it as aggregatable in index pattern listing. (Tried refreshing fields as well and upgrade from both 2.3.3 -> 5.3.1 and 5.2.2 -> 5.3.1)
The text was updated successfully, but these errors were encountered: