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

Configuring a Top Hit metric on _source throws fatal error #22770

Closed
Bargs opened this issue Sep 6, 2018 · 6 comments · Fixed by #22800
Closed

Configuring a Top Hit metric on _source throws fatal error #22770

Bargs opened this issue Sep 6, 2018 · 6 comments · Fixed by #22800
Labels
blocker bug Fixes for quality problems that affect the customer experience Feature:Visualizations Generic visualization features (in case no more specific feature label is available) Team:Visualizations Visualization editors, elastic-charts and infrastructure v6.4.1

Comments

@Bargs
Copy link
Contributor

Bargs commented Sep 6, 2018

Kibana version: master (only version I tested, could be in older versions)
Elasticsearch version: master

Describe the bug:

When I try to create a visualization with a top hit metric on the _source field I get the "Something went wrong" page

Steps to reproduce:

  1. Create a data table
  2. Configure a top hit metric on _source and hit apply
  3. Observe error screen

Screenshots (if relevant):

screen shot 2018-09-06 at 2 09 25 pm

@Bargs Bargs added bug Fixes for quality problems that affect the customer experience Feature:Visualizations Generic visualization features (in case no more specific feature label is available) triage_needed labels Sep 6, 2018
@Bargs
Copy link
Contributor Author

Bargs commented Sep 6, 2018

@elastic/kibana-visualizations

@rashmivkulkarni
Copy link
Contributor

Tried this on 6.x and able to reproduce the above bug consistently.

@timroes
Copy link
Contributor

timroes commented Sep 7, 2018

Thanks for reporting. We're on to that one and were able to reproduce it.

@marius-dr
Copy link
Member

Screenshot with the error on 5.6.12, based on Court adding it as a blocker for 5.6.12 as well.
source

@rashmivkulkarni
Copy link
Contributor

@timroes - There will be functional UI/ unit tests covering this scenario, along with the PR - correct ?

cc @LeeDr

@epixa
Copy link
Contributor

epixa commented Sep 7, 2018

@rasroh Yep, it has both. See the linked PR #22800

@timroes timroes added the Team:Visualizations Visualization editors, elastic-charts and infrastructure label Sep 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker bug Fixes for quality problems that affect the customer experience Feature:Visualizations Generic visualization features (in case no more specific feature label is available) Team:Visualizations Visualization editors, elastic-charts and infrastructure v6.4.1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants