Skip to content
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

UI warnings for using scripted fields #9175

Open
tbragin opened this issue Nov 22, 2016 · 1 comment
Open

UI warnings for using scripted fields #9175

tbragin opened this issue Nov 22, 2016 · 1 comment
Labels
Feature:Scripted Fields Scripted fields features release_note:enhancement Team:Platform-Design Team Label for Kibana Design Team. Support the Analyze group of plugins.

Comments

@tbragin
Copy link
Contributor

tbragin commented Nov 22, 2016

We have a warning about performance impact when a user defines a scripted field, but there are no indications in Discover, Visualize, Dashboard for when scripted fields are used. We should add some indicator when you are about to filter on a scripted field that it may be a potentially intensive operation.

@tbragin tbragin added Team:Platform-Design Team Label for Kibana Design Team. Support the Analyze group of plugins. Feature:Scripted Fields Scripted fields features labels Nov 22, 2016
@Bargs
Copy link
Contributor

Bargs commented Nov 29, 2016

I think sorting and visualizing on scripted fields would also be expensive operations. It would be good to get a recommendation from the design team for representing these warnings consistently anywhere they're applicable.

There's an existing warning in a tool tip on the visualize button in Discover, which might serve as a starting point.

screen shot 2016-11-29 at 3 07 53 pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Scripted Fields Scripted fields features release_note:enhancement Team:Platform-Design Team Label for Kibana Design Team. Support the Analyze group of plugins.
Projects
None yet
Development

No branches or pull requests

2 participants