# Runtime field with text type and runtime field usage within dynamic\_templates
**URL:** https://discuss.elastic.co/t/runtime-field-with-text-type-and-runtime-field-usage-within-dynamic-templates/289876
**Category:** Elasticsearch
**Tags:** runtime-fields
**Created:** [November 22, 2021, 9:19pm UTC](https://discuss.elastic.co/t/runtime-field-with-text-type-and-runtime-field-usage-within-dynamic-templates/289876 "2021-11-22T21:19:43Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@vlasami](https://discuss.elastic.co/u/vlasami)
#### Post date: [November 22, 2021, 9:19pm UTC](https://discuss.elastic.co/t/runtime-field-with-text-type-and-runtime-field-usage-within-dynamic-templates/289876/1 "2021-11-22T21:19:43Z")
Hi,
We've been experimenting with the use of the (query time) runtime fields as a possible solution for the mapping explosion problem we currently see.
Found the list of supported types for the runtime fields (Elasticsearch 7.15) and we tried out the "keyword" type.
Are there any plans to support also "text" as possible type for runtime field ? (We have some queries that would need text type in order to work)
Another question would be whether is it possible to set a dynamic\_template which would only map the fields that match a certain naming pattern to become runtime fields ?
Thanks in advance for the help!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 20, 2021, 9:20pm UTC](https://discuss.elastic.co/t/runtime-field-with-text-type-and-runtime-field-usage-within-dynamic-templates/289876/2 "2021-12-20T21:20:29Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.