# FST's in completion types

**URL:** <https://discuss.elastic.co/t/fsts-in-completion-types/25603>\
**Category:** Elasticsearch\
**Created:** [July 15, 2015, 9:52am UTC](https://discuss.elastic.co/t/fsts-in-completion-types/25603 "2015-07-15T09:52:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rodrigo](https://avatars.discourse-cdn.com/v4/letter/r/4af34b/32.png) [@rodrigo](https://discuss.elastic.co/u/rodrigo)\
**Post date:** [July 15, 2015, 9:52am UTC](https://discuss.elastic.co/t/fsts-in-completion-types/25603/1 "2015-07-15T09:52:13Z")

</div>

I have a completion field that I use to suggest city names across the world. I use the payload to return metadata (id's in a native relational DB, and a formatted output like "City - state"). Recently the consumers of the suggestor asked me to replace the "City - state" by "City, state" so I reindexed the documents with those values in the payload for the completion field. The problem is that now the suggestor returns both the old and new form, so I think due to the nature of the FST being kept in memory, I don't have an easy way to flush the old recommendations...Can I get away without a restart ? I tried a \_refresh in the index to no avail, so wondering if there is a special way to clear the old recommendations ?

---

<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:** [July 6, 2017, 12:01am UTC](https://discuss.elastic.co/t/fsts-in-completion-types/25603/2 "2017-07-06T00:01:21Z")

</div>


