# Type conflict in Elasticsearch for "record.collect.timestamp" date/long

**URL:** <https://forum.elastiflow.com/t/type-conflict-in-elasticsearch-for-record-collect-timestamp-date-long/342>\
**Category:** ElastiFlow Community\
**Tags:** elasticsearch\
**Created:** [October 28, 2025, 5:00pm UTC](https://forum.elastiflow.com/t/type-conflict-in-elasticsearch-for-record-collect-timestamp-date-long/342 "2025-10-28T17:00:05Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![dmgeurts](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.elastiflow.com/dmgeurts/32/151_2.png) [@dmgeurts](https://forum.elastiflow.com/u/dmgeurts)\
**Post date:** [October 28, 2025, 5:00pm UTC](https://forum.elastiflow.com/t/type-conflict-in-elasticsearch-for-record-collect-timestamp-date-long/342/1 "2025-10-28T17:00:05Z")

</div>

Hi all. Elasticsearch is throwing me an error about a type conflict for “record.collect.timestamp”.

```auto
This field has a type conflict
The type of the record.collect.timestamp field changes across indices and might not be available for search, visualizations, and other analysis.

Type	Indices
date	elastiflow-telemetry_flow-ecs-8.0-2.5-rollover-000001
long	elastiflow-metric-ecs-8.0-2.5-rollover

```

What type should this field be and how do I fix it as I think it’s Elastiflow that manages these index templates. I’ve deleted the indexes and they get recreated with the same types for this field.

---

<div class="post-metadata">

**Author:** ![daniel.harada](https://avatars.discourse-cdn.com/v4/letter/d/d6d6ee/32.png) [@daniel.harada](https://forum.elastiflow.com/u/daniel.harada)\
**Post date:** [October 28, 2025, 5:18pm UTC](https://forum.elastiflow.com/t/type-conflict-in-elasticsearch-for-record-collect-timestamp-date-long/342/2 "2025-10-28T17:18:21Z")

</div>

Yes, I can see that in the index mappings. Let me investigate.

 ![Screenshot 2025-10-28 at 12.17.09](https://canada1.discourse-cdn.com/flex035/uploads/elastiflow/original/1X/89ffcce234fafe4a789f7585d4171646a7fe39c3.png)

 ![Screenshot 2025-10-28 at 12.16.33](https://canada1.discourse-cdn.com/flex035/uploads/elastiflow/original/1X/414f5d8670b678dfc8f265f949604dd91203ab6f.png)

---

<div class="post-metadata">

**Author:** ![daniel.harada](https://avatars.discourse-cdn.com/v4/letter/d/d6d6ee/32.png) [@daniel.harada](https://forum.elastiflow.com/u/daniel.harada)\
**Post date:** [October 28, 2025, 5:38pm UTC](https://forum.elastiflow.com/t/type-conflict-in-elasticsearch-for-record-collect-timestamp-date-long/342/3 "2025-10-28T17:38:21Z")

</div>

The data in the ‘metrics’ table is related to the metrics from the flow collector API … [ElastiFlow Documentation](https://www.elastiflow.com/docs/monitoring/metrics)

The data in the ‘telemetry’ table is related to telemetry data from flow records.

Given that these are different data sets from different objects, the conflict in types are likely not a concern since it is unlikely that searches or visualizations would need to use both indices. If I get any feedback on this question I’ll update you here.

Regards,

Dexter

---

<div class="post-metadata">

**Author:** ![daniel.harada](https://avatars.discourse-cdn.com/v4/letter/d/d6d6ee/32.png) [@daniel.harada](https://forum.elastiflow.com/u/daniel.harada)\
**Post date:** [October 29, 2025, 12:22pm UTC](https://forum.elastiflow.com/t/type-conflict-in-elasticsearch-for-record-collect-timestamp-date-long/342/4 "2025-10-29T12:22:32Z")

</div>

To clarify, I have opened a bug ticket to get the ‘metric’ index template corrected. The ‘`record.collect.timestamp`’ type should be `Date`.

Thanks for asking!

Regards,

Dexter

---

<div class="post-metadata">

**Author:** ![dmgeurts](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.elastiflow.com/dmgeurts/32/151_2.png) [@dmgeurts](https://forum.elastiflow.com/u/dmgeurts)\
**Post date:** [October 29, 2025, 2:57pm UTC](https://forum.elastiflow.com/t/type-conflict-in-elasticsearch-for-record-collect-timestamp-date-long/342/5 "2025-10-29T14:57:00Z")

</div>

That’s good to know. However, this would mean I’m probably reading the instructions wrong regarding datasets. For which I can no longer find the instructions I was looking at two weeks ago…

Thank you for clarifying.

---

<div class="post-metadata">

**Author:** ![system](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.elastiflow.com/system/32/59_2.png) [@system](https://forum.elastiflow.com/u/system)\
**Post date:** [November 28, 2025, 2:57pm UTC](https://forum.elastiflow.com/t/type-conflict-in-elasticsearch-for-record-collect-timestamp-date-long/342/6 "2025-11-28T14:57:38Z")

</div>

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