# Can we specify other data type in grok processor in the future?

**URL:** <https://discuss.elastic.co/t/can-we-specify-other-data-type-in-grok-processor-in-the-future/67149>\
**Category:** Elasticsearch\
**Created:** [November 25, 2016, 3:07am UTC](https://discuss.elastic.co/t/can-we-specify-other-data-type-in-grok-processor-in-the-future/67149 "2016-11-25T03:07:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ginger](https://avatars.discourse-cdn.com/v4/letter/g/34f0e0/32.png) [@ginger](https://discuss.elastic.co/u/ginger)\
**Post date:** [November 25, 2016, 3:07am UTC](https://discuss.elastic.co/t/can-we-specify-other-data-type-in-grok-processor-in-the-future/67149/1 "2016-11-25T03:07:18Z")

</div>

Hi.  
Ingest node is a elegant solution for ingest data. When specify a grok pattern, I have a little trouble.

The syntax for reusing a grok pattern comes in three forms: %{SYNTAX:SEMANTIC}, %{SYNTAX}, %{SYNTAX:SEMANTIC:TYPE}. TYPE is the type you wish to cast your named field, but only int and float are currently supported for coercion.

I wonder that If TYPE have plan to support other data type in the future? Or have other elegant way in which I can specify data type for fields?

---

<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:** [December 23, 2016, 3:07am UTC](https://discuss.elastic.co/t/can-we-specify-other-data-type-in-grok-processor-in-the-future/67149/2 "2016-12-23T03:07:24Z")

</div>

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