[Kibana][Visualization][Bug & feature request] Kibana vertical bar doesn't show extended bounds correctly when use 2 depth aggs (histogram -> terms) with empty bucket settings

[kunisen]

Kibana version:
5.5.0 ~ 6.4

Elasticsearch version:
5.5.0 ~ 6.4

Server OS version:
Major OS

Browser version:
Major browser

Browser OS version:
Latest ver

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

Describe the bug:
Kibana vertical bar doesn't show extended bounds correctly when use 2 depth aggs (histogram -> terms) with empty bucket settings.
We can see empty buckets returned from visualization spy - response.
So it is considered that Kibana didn't draw those empty buckets in such kind of situation.

Steps to reproduce:
[1] Download and install Elasticsearch and Kibana 5.5.0

[2] Bulk insert the following data

POST _bulk
{"index":{"_index":"test_index","_type":"logs","_id":"5"}}
{"score":35,"model":"XX-2000"}
{"index":{"_index":"test_index","_type":"logs","_id":"8"}}
{"score":49,"model":"XX-3000"}
{"index":{"_index":"test_index","_type":"logs","_id":"9"}}
{"score":51,"model":"XX-3000"}
{"index":{"_index":"test_index","_type":"logs","_id":"10"}}
{"score":67,"model":"XX-3000"}
{"index":{"_index":"test_index","_type":"logs","_id":"2"}}
{"score":50,"model":"XX-2000"}
{"index":{"_index":"test_index","_type":"logs","_id":"4"}}
{"score":30,"model":"XX-2000"}
{"index":{"_index":"test_index","_type":"logs","_id":"6"}}
{"score":32,"model":"XX-3000"}
{"index":{"_index":"test_index","_type":"logs","_id":"1"}}
{"score":60,"model":"XX-2000"}
{"index":{"_index":"test_index","_type":"logs","_id":"7"}}
{"score":38,"model":"XX-3000"}
{"index":{"_index":"test_index","_type":"logs","_id":"3"}}
{"score":44,"model":"XX-2000"}

[3] Create index-pattern, visualization in Kibana

Expected behavior:

As we can see the empty bucket response returned from visualization spy response.

Actual behavior:

No extended bounds shown here.

Errors in browser console (if relevant):

No errors.

Any additional context:

If we drag and drop the order of Split Series - Terms aggs higher than Historgram, then we can get the extended bounds correctly displayed.

[kunisen]

any updates here?

[lposani]

Would be nice to have updates on this.

[flash1293]

This is still a valid problem caused by the way we turn the Elasticsearch response into a table - in case of bucketing by terms first, there are buckets with 0 doc count for the extended bounds of the histogram, but if histogram is done first, the "extended buckets" of the histogram agg are completely empty (because the terms agg doesn't have any documents to operate on).

I traced this back and it should be fixable by adding the extended bounds of a histogram dimension to the params here along with the interval:

kibana/src/plugins/vis_types/xy/public/to_ast.ts

Line 186 in fa59b52

(dimensions.x.params as HistogramParams).interval = output.params.interval;

Then use it to define the x domain here:

kibana/src/plugins/vis_types/xy/public/utils/domain.ts

Lines 75 to 76 in cb86892

	}

[flash1293]

Blocked on #119474

[flash1293]

Fixed by #134020 - it's now possible to specify the extents of the x axis in this scenario in Lens to keep it stable independently of the data