# beat.Event and big.Int mapping

**URL:** <https://discuss.elastic.co/t/beat-event-and-big-int-mapping/149197>\
**Category:** Beats\
**Tags:** beats-development\
**Created:** [September 19, 2018, 9:32pm UTC](https://discuss.elastic.co/t/beat-event-and-big-int-mapping/149197 "2018-09-19T21:32:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![paulkeogh](https://avatars.discourse-cdn.com/v4/letter/p/8dc957/32.png) [@paulkeogh](https://discuss.elastic.co/u/paulkeogh)\
**Post date:** [September 19, 2018, 9:32pm UTC](https://discuss.elastic.co/t/beat-event-and-big-int-mapping/149197/1 "2018-09-19T21:32:02Z")

</div>

libbeats seems to map \*big.Int types to strings when publishing - is there any way I can force this to a numeric type by using \_meta/fields.yml configuration ?

---

<div class="post-metadata">

**Author:** ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)\
**Post date:** [September 22, 2018, 1:48pm UTC](https://discuss.elastic.co/t/beat-event-and-big-int-mapping/149197/2 "2018-09-22T13:48:40Z")

</div>

Hi @paulkeogh,

Yes, in principle you should be able to define it as a `long` in `_meta/fields.yml`. Did you try that?  
I have found that with recent versions of libbeat this file is being ignored ([#8397](https://github.com/elastic/beats/pull/8397)), if this is your case, try to move `_meta/fields.yml` to `_meta/fields.common.yml` and run `make update`, then setup your index templates again.

---

<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 20, 2018, 1:48pm UTC](https://discuss.elastic.co/t/beat-event-and-big-int-mapping/149197/3 "2018-10-20T13:48:53Z")

</div>

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