# Unable to add custom analyzer

**URL:** <https://discuss.elastic.co/t/unable-to-add-custom-analyzer/293373>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [January 3, 2022, 4:37pm UTC](https://discuss.elastic.co/t/unable-to-add-custom-analyzer/293373 "2022-01-03T16:37:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![maviles](https://avatars.discourse-cdn.com/v4/letter/m/ccd318/32.png) [@maviles](https://discuss.elastic.co/u/maviles)\
**Post date:** [January 3, 2022, 4:37pm UTC](https://discuss.elastic.co/t/unable-to-add-custom-analyzer/293373/1 "2022-01-03T16:37:38Z")

</div>

Greetings, I'm unable to add a custom analyzer "tokenizer" to an existing, up and running index. I'm able to add the same custom analyzer creating a new index and reindexing an old one to a recently created one. However, this configuration does meet our requirement because data of the filebeat will continue arriving in the old index.

PUT filebeat\_new

{ "mappings": {

```
"properties": {

  "my_text": {

    "type": "text",

    "analyzer": "my_custom_analyzer2" 

   }

 }

```

}

}

---

<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:** [January 31, 2022, 6:37pm UTC](https://discuss.elastic.co/t/unable-to-add-custom-analyzer/293373/2 "2022-01-31T18:37:49Z")

</div>

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