# Native IntegerRange type in Elastic.Clients (8.9) does not serialize correctly

**URL:** <https://discuss.elastic.co/t/native-integerrange-type-in-elastic-clients-8-9-does-not-serialize-correctly/341581>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [August 24, 2023, 2:26pm UTC](https://discuss.elastic.co/t/native-integerrange-type-in-elastic-clients-8-9-does-not-serialize-correctly/341581 "2023-08-24T14:26:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mathemaphysics](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mathemaphysics/32/120925_2.png) [@Mathemaphysics](https://discuss.elastic.co/u/Mathemaphysics)\
**Post date:** [August 24, 2023, 2:26pm UTC](https://discuss.elastic.co/t/native-integerrange-type-in-elastic-clients-8-9-does-not-serialize-correctly/341581/1 "2023-08-24T14:26:47Z")

</div>

When I use `IntegerRange` it does not serialize to fields named `gt`, `gte`, `lt`, and `lte`.

I have an index template which sends my field `item_index_range` to an explicit `integer_range` type. I shouldn't need to do any mapping at all. It puts it in as my class name `itemIndexRange` and my template doesn't know what that is.

Is there something I'm missing? Is this a bug?

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/9/f9e0507a6704c0a1851e353405b7003d889b5a63.png)

---

<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:** [September 22, 2023, 1:18pm UTC](https://discuss.elastic.co/t/native-integerrange-type-in-elastic-clients-8-9-does-not-serialize-correctly/341581/3 "2023-09-22T13:18:42Z")

</div>

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