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

Coordinates Map visualization re-creating geohashLayer on map move #12919

Closed
nreese opened this issue Jul 17, 2017 · 0 comments · Fixed by #12931
Closed

Coordinates Map visualization re-creating geohashLayer on map move #12919

nreese opened this issue Jul 17, 2017 · 0 comments · Fixed by #12931
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Visualizations Generic visualization features (in case no more specific feature label is available) PR sent regression v6.0.0-beta1

Comments

@nreese
Copy link
Contributor

nreese commented Jul 17, 2017

Kibana version: 6.0.0-beta1

Elasticsearch version: 6.0.0-beta1

Server OS version: macOS

Browser version: chrome

Browser OS version: macOS

Original install method (e.g. download page, yum, from source, etc.): from source

Description of the problem including expected versus actual behavior:
Every time the map moves, maps_visualizations calls _recreateGeohashLayer function, even in cases when a new _msearch was not issued.

@nreese nreese added Feature:Visualizations Generic visualization features (in case no more specific feature label is available) bug Fixes for quality problems that affect the customer experience v6.0.0-beta1 labels Jul 17, 2017
@thomasneirynck thomasneirynck self-assigned this Jul 17, 2017
This was referenced Jul 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Visualizations Generic visualization features (in case no more specific feature label is available) PR sent regression v6.0.0-beta1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants