# Force external tokenization/lemmatization

**URL:** <https://discuss.elastic.co/t/force-external-tokenization-lemmatization/123761>\
**Category:** Elasticsearch\
**Created:** [March 13, 2018, 3:19pm UTC](https://discuss.elastic.co/t/force-external-tokenization-lemmatization/123761 "2018-03-13T15:19:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![levi-strauss](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@levi-strauss](https://discuss.elastic.co/u/levi-strauss)\
**Post date:** [March 13, 2018, 3:19pm UTC](https://discuss.elastic.co/t/force-external-tokenization-lemmatization/123761/1 "2018-03-13T15:19:02Z")

</div>

Hi,

is there any other way to force custom tokenization and lemmatization besides writing a custom Token Filter plugin?

I would like to synchronize products of custom analysis (done first) with data stored in elasticsearch using a text type (done second). My aim is to use elastic for fulltext search and highlight.

I've been playing with the ingest node, but I can't see any way to force tokenization/lemmatization using processors. (I was hoping to combine somehow the two streams of tokens and lemmas into a searchable text field.) Do I have the right impression?

Thanks in advance for any suggestions or tips,

ls

---

<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 10, 2018, 3:19pm UTC](https://discuss.elastic.co/t/force-external-tokenization-lemmatization/123761/2 "2018-04-10T15:19:13Z")

</div>

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