# Auto-configure fields as term\_vectors if they cross max length

**URL:** <https://discuss.elastic.co/t/auto-configure-fields-as-term-vectors-if-they-cross-max-length/183834>\
**Category:** Elasticsearch\
**Created:** [June 1, 2019, 8:45pm UTC](https://discuss.elastic.co/t/auto-configure-fields-as-term-vectors-if-they-cross-max-length/183834 "2019-06-01T20:45:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![elk11](https://avatars.discourse-cdn.com/v4/letter/e/45deac/32.png) [@elk11](https://discuss.elastic.co/u/elk11)\
**Post date:** [June 1, 2019, 8:45pm UTC](https://discuss.elastic.co/t/auto-configure-fields-as-term-vectors-if-they-cross-max-length/183834/1 "2019-06-01T20:45:09Z")

</div>

Hi,

I see many of the fields in my indices have large text data. Because of this after upgrading from 5.x to 7.0 I'm seeing shard failures in kibana.

I found that i can use term\_vector for such field in the index mapping.

Is there a way to auto configure mappings such that fields violating max\_length are configured as term\_vectors?

Is there a way to update mapping with term\_vector or the indices have to be reindexed?

---

<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:** [June 29, 2019, 8:45pm UTC](https://discuss.elastic.co/t/auto-configure-fields-as-term-vectors-if-they-cross-max-length/183834/2 "2019-06-29T20:45:13Z")

</div>

Closed on June 29, 2019, 8:45pm UTC

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