# How to properly add an ngram tokenizer via Nest

**URL:** <https://discuss.elastic.co/t/how-to-properly-add-an-ngram-tokenizer-via-nest/329777>\
**Category:** Elasticsearch\
**Tags:** language-clients\
**Created:** [April 11, 2023, 9:05pm UTC](https://discuss.elastic.co/t/how-to-properly-add-an-ngram-tokenizer-via-nest/329777 "2023-04-11T21:05:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jfavaro](https://avatars.discourse-cdn.com/v4/letter/j/eb8c5e/32.png) [@jfavaro](https://discuss.elastic.co/u/jfavaro)\
**Post date:** [April 11, 2023, 9:05pm UTC](https://discuss.elastic.co/t/how-to-properly-add-an-ngram-tokenizer-via-nest/329777/1 "2023-04-11T21:05:22Z")

</div>

We have an existing Elastic version 8.3.3 with a .Net implementation using Nest 7.17.5.

I've been trying to add a new field utitlizing an ngram tokenizer but whenever I add the code to my analyzers the existing full\_autocomplete analyzer is failing to be recognized.

`"query_shard_exception\",\"reason\":\"[multi_match] analyzer [full_autocomplete] not found\"`

As far as I can tell from reviewing documentation and other forum questions I'm formatting this correctly. Can anyone point out where I might be going wrong?

[Code example in case the embed link fails.](https://gist.github.com/jafavaro/2b80decbe551a71e6977a147df79f0c1)  
If I remove the ngram code and reindex the full\_autocomplete analyzer works again.

Thanks for your help in advance.

---

<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:** [May 9, 2023, 9:05pm UTC](https://discuss.elastic.co/t/how-to-properly-add-an-ngram-tokenizer-via-nest/329777/2 "2023-05-09T21:05:35Z")

</div>

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