# Timeseries indices has type both string and text(or keyword)

**URL:** <https://discuss.elastic.co/t/timeseries-indices-has-type-both-string-and-text-or-keyword/77992>\
**Category:** Kibana\
**Created:** [March 9, 2017, 2:00pm UTC](https://discuss.elastic.co/t/timeseries-indices-has-type-both-string-and-text-or-keyword/77992 "2017-03-09T14:00:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![no\_jihun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/no_jihun/32/64028_2.png) [@no\_jihun](https://discuss.elastic.co/u/no_jihun)\
**Post date:** [March 9, 2017, 2:00pm UTC](https://discuss.elastic.co/t/timeseries-indices-has-type-both-string-and-text-or-keyword/77992/1 "2017-03-09T14:00:24Z")

</div>

I am preparing upgrade elastic stack from 2.3 to 5.2.  
My question is...  
Index dailylog.20170311(created by es 2.3) has string field "subject".  
what happen if dailylog.20170312(will created by es 5.2) will have keyword or text field "subject"?

usually kibana complains type conflict.  
What about this case? do I need to reindex 20170311 before serving?

---

<div class="post-metadata">

**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\
**Post date:** [March 9, 2017, 8:46pm UTC](https://discuss.elastic.co/t/timeseries-indices-has-type-both-string-and-text-or-keyword/77992/2 "2017-03-09T20:46:19Z")

</div>

> [@no\_jihun](#):
>
> do I need to reindex 20170311 before serving?

I don't think so, Kibana should treat all of the "string" type fields (text and keyword included) the same. At least I think that's the case.

However, if you want to be ready for upgrading to 6.0 or later, you'll need to re-index your string fields into either text or keyword, as appropriate. It might be worthwhile to do it as part of your 5.2 upgrade so you don't have to worry about it later.

---

<div class="post-metadata">

**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\
**Post date:** [March 9, 2017, 8:54pm UTC](https://discuss.elastic.co/t/timeseries-indices-has-type-both-string-and-text-or-keyword/77992/3 "2017-03-09T20:54:04Z")

</div>

I would also recommend installing and checking the [Elasticsearch Migration Plugin](https://github.com/elastic/elasticsearch-migration/tree/2.x) to identify issues.

---

<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:** [April 6, 2017, 8:54pm UTC](https://discuss.elastic.co/t/timeseries-indices-has-type-both-string-and-text-or-keyword/77992/4 "2017-04-06T20:54:35Z")

</div>

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