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

Add warning for infinite values in a range aggregation #36558

Closed
alexfrancoeur opened this issue May 14, 2019 · 3 comments · Fixed by #38531
Closed

Add warning for infinite values in a range aggregation #36558

alexfrancoeur opened this issue May 14, 2019 · 3 comments · Fixed by #38531
Labels
Feature:Vis Editor Visualization editor issues Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@alexfrancoeur
Copy link

When building a visualization that uses a range aggregation, an empty value is an infinite value. This is not obvious to all users. It'd be nice to provide a warning for empty values letting the user know that they're about to query to +/- infinity.

image

@alexfrancoeur alexfrancoeur added discuss Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Vis Editor Visualization editor issues labels May 14, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app

@timroes
Copy link
Contributor

timroes commented May 23, 2019

I would suggest we just use -∞ and +∞ as a placeholder for the from respective to box. So if the user doesn't enter anything in there, they see that it will default to that value. @maryia-lapata @sulemanof Maybe we could address that when moving over the Range control over to React in the same step?

@maryia-lapata
Copy link
Contributor

@timroes yes, of course, we will address this issue during Range control migration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Vis Editor Visualization editor issues Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants