# Doesn't a field support multiple types?

**URL:** <https://discuss.elastic.co/t/doesnt-a-field-support-multiple-types/289271>\
**Category:** Elasticsearch\
**Created:** [November 16, 2021, 7:22am UTC](https://discuss.elastic.co/t/doesnt-a-field-support-multiple-types/289271 "2021-11-16T07:22:47Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![wajika](https://avatars.discourse-cdn.com/v4/letter/w/977dab/32.png) [@wajika](https://discuss.elastic.co/u/wajika)\
**Post date:** [November 16, 2021, 7:22am UTC](https://discuss.elastic.co/t/doesnt-a-field-support-multiple-types/289271/1 "2021-11-16T07:22:47Z")

</div>

> org.elasticsearch.index.mapper.MapperParsingException: object mapping for [http.request.body.original] tried to parse field [original] as object, but found a concrete value

I plan to convert the http.request.body.original field generated by apm to the object type, but es prompts it to be a concrete value. Sometimes the original is a json, and sometimes it is a string of ordinary strings (such as xxxxyyyy122 ).

I need to parse it out when original is json type, How to configure mapping in this case?

In addition, I added the Dynamic option to originl, but it didn’t work either

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 16, 2021, 11:27pm UTC](https://discuss.elastic.co/t/doesnt-a-field-support-multiple-types/289271/2 "2021-11-16T23:27:31Z")

</div>

No, a field doesn't support multiple types.

You might be better off setting this as a keyword?

---

<div class="post-metadata">

**Author:** ![wajika](https://avatars.discourse-cdn.com/v4/letter/w/977dab/32.png) [@wajika](https://discuss.elastic.co/u/wajika)\
**Post date:** [November 17, 2021, 1:11am UTC](https://discuss.elastic.co/t/doesnt-a-field-support-multiple-types/289271/3 "2021-11-17T01:11:13Z")

</div>

Are there any benefits to using keyword?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 17, 2021, 1:48am UTC](https://discuss.elastic.co/t/doesnt-a-field-support-multiple-types/289271/4 "2021-11-17T01:48:06Z")

</div>

You won't run into this problem 🙂

---

<div class="post-metadata">

**Author:** ![wajika](https://avatars.discourse-cdn.com/v4/letter/w/977dab/32.png) [@wajika](https://discuss.elastic.co/u/wajika)\
**Post date:** [November 17, 2021, 2:23am UTC](https://discuss.elastic.co/t/doesnt-a-field-support-multiple-types/289271/5 "2021-11-17T02:23:52Z")

</div>

![image](https://us1.discourse-cdn.com/elastic/original/3X/d/c/dc36caa83f2003fd3cc0ff47e9f1ada45349b30e.png)  
I added mapping for json to this field, but apm returns as "[REDACTED]" by default, which destroys the mapping and es will not write this data. Is there any way to filter out "[REDACTED]"?

---

<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 15, 2021, 2:24am UTC](https://discuss.elastic.co/t/doesnt-a-field-support-multiple-types/289271/6 "2021-12-15T02:24:27Z")

</div>

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