-
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
Only include scripted fields if really needed in request #18564
Comments
Are you seeing any issues as a result? Since the visualization request is asking for 0 hits, I would assume the script isn't actually being run at all. |
No, no issues, just didn't expect it to be part of the request. |
Gotcha. In that case I'd only really want to exclude it if it doesn't overly complicate the code. I'll leave this open as a chore task. |
Per recent report, this is actually causing issues, so removing Chore label and reclassifying as bug. |
I believe the Elasticsearch team is discussing some of this on their end as well - elastic/elasticsearch#31824 |
Elasticsearch merged a fix for this elastic/elasticsearch#31824 @elastic/kibana-app |
Yeah since the Elasticsearch team no longer calculates scripted fields in case we send |
Kibana version: 6.2.3
Elasticsearch version: 6.2.3
Server OS version: OSX
Browser version: Chrome
Browser OS version: 65.0.3325.181 (Official Build) (64-bit)
Original install method (e.g. download page, yum, from source, etc.): tar
Description of the problem including expected versus actual behavior: If an index pattern has a scripted field associated with it, then any Kibana requests related to that index pattern (visualizations, dashboards, etc.) will include that scripted field as part of the request, even if the request does not require the scripted field.
Steps to reproduce:
The text was updated successfully, but these errors were encountered: