When transitioning from an ES|QL query to another, if the landing one provides an empty table as result, then the current visualization configuration is cleaned up and the "ideal" suggestion candidate is not taking over the old visualization.
Not sure if anything can be suggested here without any data, but the current behaviour is confusing (as it also allows for saving the invalid chart config with no dimensions).
Describe the bug:
When transitioning from an
ES|QL
query to another, if the landing one provides an empty table as result, then the current visualization configuration is cleaned up and the "ideal" suggestion candidate is not taking over the old visualization.Not sure if anything can be suggested here without any data, but the current behaviour is confusing (as it also allows for saving the invalid chart config with no dimensions).