# Analyzer in ingest node

**URL:** <https://discuss.elastic.co/t/analyzer-in-ingest-node/214619>\
**Category:** Elasticsearch\
**Created:** [January 10, 2020, 3:13pm UTC](https://discuss.elastic.co/t/analyzer-in-ingest-node/214619 "2020-01-10T15:13:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rvanegmond](https://avatars.discourse-cdn.com/v4/letter/r/3ec8ea/32.png) [@rvanegmond](https://discuss.elastic.co/u/rvanegmond)\
**Post date:** [January 10, 2020, 3:13pm UTC](https://discuss.elastic.co/t/analyzer-in-ingest-node/214619/1 "2020-01-10T15:13:05Z")

</div>

I'm looking for a way to use the (for example path\_hierarchy) tokenizer(s) in a ingest pipeline. Is there anyway of doing this?

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [January 13, 2020, 1:45pm UTC](https://discuss.elastic.co/t/analyzer-in-ingest-node/214619/2 "2020-01-13T13:45:22Z")

</div>

Hey,

the tokenizer are only applied before a document is indexed. The ingest pipeline modifies the JSON before indexing starts (this is also the reason why you can dedicated ingest nodes, as these functions are split from each other).

I guess you could come up with a `script` processor that is doing some splitting based on a character and thus create something similar than the path hierarchy tokenizer.

--Alex

---

<div class="post-metadata">

**Author:** ![rvanegmond](https://avatars.discourse-cdn.com/v4/letter/r/3ec8ea/32.png) [@rvanegmond](https://discuss.elastic.co/u/rvanegmond)\
**Post date:** [January 16, 2020, 3:06pm UTC](https://discuss.elastic.co/t/analyzer-in-ingest-node/214619/3 "2020-01-16T15:06:01Z")

</div>

Thanks! Might be nice to be able to leverage the function behind the tokenizers instead of building them again in regex 😉

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [January 20, 2020, 4:10pm UTC](https://discuss.elastic.co/t/analyzer-in-ingest-node/214619/4 "2020-01-20T16:10:46Z")

</div>

Please go ahead and open an issue in the elasticsearch repo about this, explaining the rationale behind it!

--Alex

---

<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:** [February 17, 2020, 4:10pm UTC](https://discuss.elastic.co/t/analyzer-in-ingest-node/214619/5 "2020-02-17T16:10:46Z")

</div>

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