Describe the bug
When using the Heatmap spec with a time scale, the bucket values are trivial computed and don't always align with the values on the data. This causes charts to render without the cells that should appear the in given domain.
Expected behavior
Min and max domain values should be extended to include the full extent of partial buckets. This could be done using the timeScale.rawTcks.
Screenshots
Version (please complete the following information):
This is also related to handling partial time buckets in heatmap. Now lens is just increasing the domain to include the partial buckets as if they were full buckets which is not ideal. See https://github.com/elastic/kibana/pull/97978/files/6283fb0d54cfa1c8e482ffad4b249e294750f02a..356109c161583af3ec60a69be57c2e96e1521cc5#diff-ecf0195846e85c9002680a385d9afe155d27ad5de1c696bdf5f08101201a440fR88-R100
Kibana Cross Issues
elastic/kibana#97978 (comment)
Describe the bug
When using the
Heatmapspec with a time scale, the bucket values are trivial computed and don't always align with the values on the data. This causes charts to render without the cells that should appear the in given domain.Expected behavior
Min and max domain values should be extended to include the full extent of partial buckets. This could be done using the
timeScale.rawTcks.Screenshots
Version (please complete the following information):
@latestThis is also related to handling partial time buckets in heatmap. Now lens is just increasing the domain to include the partial buckets as if they were full buckets which is not ideal. See https://github.com/elastic/kibana/pull/97978/files/6283fb0d54cfa1c8e482ffad4b249e294750f02a..356109c161583af3ec60a69be57c2e96e1521cc5#diff-ecf0195846e85c9002680a385d9afe155d27ad5de1c696bdf5f08101201a440fR88-R100
Kibana Cross Issues
elastic/kibana#97978 (comment)