# Runtime Fields

**URL:** <https://discuss.elastic.co/t/runtime-fields/285142>\
**Category:** Elasticsearch\
**Tags:** runtime-fields\
**Created:** [September 25, 2021, 8:03pm UTC](https://discuss.elastic.co/t/runtime-fields/285142 "2021-09-25T20:03:25Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Swapnadeep\_Mondal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swapnadeep_mondal/32/92703_2.png) [@Swapnadeep\_Mondal](https://discuss.elastic.co/u/Swapnadeep_Mondal)\
**Post date:** [September 25, 2021, 8:03pm UTC](https://discuss.elastic.co/t/runtime-fields/285142/1 "2021-09-25T20:03:25Z")

</div>

According to documentation runtime fields are not indexed. Now if one field is not indexed then it will not searchable or queryable. but then I query on a runtime field it returned me results instead showing "Cannot search on-field since it is not indexed". why? I am understanding something wrong?

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [September 25, 2021, 8:18pm UTC](https://discuss.elastic.co/t/runtime-fields/285142/2 "2021-09-25T20:18:22Z")

</div>

Runtime fields break that rule.

---

<div class="post-metadata">

**Author:** ![Swapnadeep\_Mondal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swapnadeep_mondal/32/92703_2.png) [@Swapnadeep\_Mondal](https://discuss.elastic.co/u/Swapnadeep_Mondal)\
**Post date:** [September 26, 2021, 2:43pm UTC](https://discuss.elastic.co/t/runtime-fields/285142/3 "2021-09-26T14:43:17Z")

</div>

Can you please explain more?  
How it is breaking that rule? Means how it is searchable even tho it is not indexed?

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [September 26, 2021, 3:19pm UTC](https://discuss.elastic.co/t/runtime-fields/285142/4 "2021-09-26T15:19:29Z")

</div>

Hi @Swapnadeep_Mondal Welcome to the community.

Runtime Fields allow schema on read and now Elasticsearch supports that. Yes this is a big new powerful feature that's been added fundamentally changes the way you can work with data in Elasticsearch.

In short you can use runtime fields anywhere you would use a normal index fields there may be some performance impact in some cases and that would be the trade-off.

I suggest you read these and give it a try

This Blog

> **[Introducing Elasticsearch runtime fields](https://www.elastic.co/blog/introducing-elasticsearch-runtime-fields)**
>
> In 7.11, we’re excited to announce schema on read in the Elastic Stack. We now offer the best of both worlds on a single platform. Schema on read for flexibility and schema on write for performance. We call our implementation runtime fields.

The Reference Docs

> **[Map a runtime field | Elasticsearch Guide \[7.15\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/runtime-mapping-fields.html)**

Kibana

> **[Discover | Kibana Guide \[7.15\] | Elastic](https://www.elastic.co/guide/en/kibana/current/discover.html#add-field-in-discover)**

Give it a try...

---

<div class="post-metadata">

**Author:** ![Swapnadeep\_Mondal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swapnadeep_mondal/32/92703_2.png) [@Swapnadeep\_Mondal](https://discuss.elastic.co/u/Swapnadeep_Mondal)\
**Post date:** [September 26, 2021, 4:27pm UTC](https://discuss.elastic.co/t/runtime-fields/285142/5 "2021-09-26T16:27:01Z")

</div>

Thank you all. appreciate it.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 24, 2021, 4:27pm UTC](https://discuss.elastic.co/t/runtime-fields/285142/6 "2021-10-24T16:27:21Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
