# A kibana query with hot-warm-cold node

**URL:** <https://discuss.elastic.co/t/a-kibana-query-with-hot-warm-cold-node/201919>\
**Category:** Kibana\
**Created:** [October 2, 2019, 9:15am UTC](https://discuss.elastic.co/t/a-kibana-query-with-hot-warm-cold-node/201919 "2019-10-02T09:15:42Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\
**Post date:** [October 2, 2019, 2:22pm UTC](https://discuss.elastic.co/t/a-kibana-query-with-hot-warm-cold-node/201919/2 "2019-10-02T14:22:49Z")

</div>

Kibana should be doing a range query, so this may explain

> [@Are shards skipped when a range query does not create hits](https://discuss.elastic.co/t/are-shards-skipped-when-a-range-query-does-not-create-hits/120239):
>
> In my templated mapping, I use a sort.field on a datetime field. That datetime field thus contains increasing values for the rows inserted during the day. I rollover daily, and do a force merge on older indices. I want to know if doing a range query on the datetime will know it can skip some indices based on the min and max value of the datetime field. I.e. not even having to talk to the shard(s). I found nothing in the doc or discussion forums. If I do a "profile":true in Kibana's dev tools,…

Is your 15 minute query pretty fast?

---

_[View the full topic](https://discuss.elastic.co/t/a-kibana-query-with-hot-warm-cold-node/201919)._