# Custom Analyzer deployment

**URL:** <https://discuss.elastic.co/t/custom-analyzer-deployment/125772>\
**Category:** Elasticsearch\
**Created:** [March 27, 2018, 2:05pm UTC](https://discuss.elastic.co/t/custom-analyzer-deployment/125772 "2018-03-27T14:05:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tobsucht](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tobsucht/32/29265_2.png) [@Tobsucht](https://discuss.elastic.co/u/Tobsucht)\
**Post date:** [March 27, 2018, 2:05pm UTC](https://discuss.elastic.co/t/custom-analyzer-deployment/125772/1 "2018-03-27T14:05:34Z")

</div>

As my requirements for the analysis process is pretty unique, I have written multiple custom analyzers and registered them as a plugin in elasticsearch. This is working, but I don't really like the process of having to deploy the plugin for every bugfix/code addition/ES version upgrade, besides patches for my application.

I have read through the docs and there seems no way to deploy a custom analyzer just in my application, am I right? Just an interface between a lucene analyzer in an application and a elastic node.

To accomplish that, I thought about serializing the output of my analyzers to a token format like term:positionInc:posLength and just install an analyzer within elasticsearch which can read this format. This would reduce the frequency of updating the plugin in ES just for version upgrades.

Is that a bad idea? Does a solution like this already exist?

---

<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 24, 2018, 2:05pm UTC](https://discuss.elastic.co/t/custom-analyzer-deployment/125772/2 "2018-04-24T14:05:49Z")

</div>

Closed on April 24, 2018, 2:05pm UTC

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