# Elasticsearch processing pipeline capability? **URL:** \ **Category:** Elasticsearch\ **Created:** [August 26, 2014, 8:41pm UTC](https://discuss.elastic.co/t/elasticsearch-processing-pipeline-capability/19475 "2014-08-26T20:41:35Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Kevin\_Blaisdell](https://avatars.discourse-cdn.com/v4/letter/k/e9c0ed/32.png) [@Kevin\_Blaisdell](https://discuss.elastic.co/u/Kevin_Blaisdell)\ **Post date:** [August 26, 2014, 8:41pm UTC](https://discuss.elastic.co/t/elasticsearch-processing-pipeline-capability/19475/1 "2014-08-26T20:41:35Z")
Is there any facility in elasticsearch to help with sending terms to an external processes after lucene processing (tokenization, filters, etc)? The idea here is having some external analysis / nlp code run against the documents while keeping all the pre-processing choices consistent and in one place (i.e. the analysis setup in elasticsearch index configuration). I am not very familiar with Lucene, but I believe possibly their update request processor is intended for scenarios like this needing a simple pipeline. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/6f60301e-3fe0-4c90-8645-24a18e165a46%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6f60301e-3fe0-4c90-8645-24a18e165a46%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [August 26, 2014, 9:56pm UTC](https://discuss.elastic.co/t/elasticsearch-processing-pipeline-capability/19475/2 "2014-08-26T21:56:04Z")
If you want to retrieve the term list of an index after Lucene processing via REST HTTP API, you can try > **[GitHub - jprante/elasticsearch-index-termlist: Elasticsearch Index Termlist](https://github.com/jprante/elasticsearch-index-termlist)** > > Elasticsearch Index Termlist. Contribute to jprante/elasticsearch-index-termlist development by creating an account on GitHub. Jörg On Tue, Aug 26, 2014 at 10:41 PM, Kevin B [blaisdellk@gmail.com](mailto:blaisdellk@gmail.com) wrote: > Is there any facility in elasticsearch to help with sending terms to an > external processes after lucene processing (tokenization, filters, etc)? > The idea here is having some external analysis / nlp code run against the > documents while keeping all the pre-processing choices consistent and in > one place (i.e. the analysis setup in elasticsearch index configuration). > > I am not very familiar with Lucene, but I believe possibly their update > request processor is intended for scenarios like this needing a simple > pipeline. > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/6f60301e-3fe0-4c90-8645-24a18e165a46%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6f60301e-3fe0-4c90-8645-24a18e165a46%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/6f60301e-3fe0-4c90-8645-24a18e165a46%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/6f60301e-3fe0-4c90-8645-24a18e165a46%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGQ1NaTJn31H%3DTn7xLQTwagXWSDT5vM3xDLtt9wfcTaTw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGQ1NaTJn31H%3DTn7xLQTwagXWSDT5vM3xDLtt9wfcTaTw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Kevin\_Blaisdell](https://avatars.discourse-cdn.com/v4/letter/k/e9c0ed/32.png) [@Kevin\_Blaisdell](https://discuss.elastic.co/u/Kevin_Blaisdell)\ **Post date:** [September 5, 2014, 6:35pm UTC](https://discuss.elastic.co/t/elasticsearch-processing-pipeline-capability/19475/3 "2014-09-05T18:35:07Z")
Jorg, Thanks. I actually have used the term list plugin (thanks) for some quick prototype / experiments. I actually meant I am not familiar with SOLR. Lucene I do have some familiarity with. In this case I was wanting to really be able to send the analysed text on to some post processing either in parallel or prior to indexing. I can have the other process load up the same sets of analyser config being used by ES with lucene, but then I have to manage 2 sets of analysis configuration (external process + es) plus I am making 2 passes on the data. Or I can come back and hit the index after it is built with maybe the term vector api, but again 2 passes on the data. From the lack of response I am guessing there isn't a facility for this. I am surprised because I figured a lot of people would be running various things over their text data to better analyse it, but I might also be approaching it wrong. Thanks again! Kevin On Tuesday, August 26, 2014 4:56:10 PM UTC-5, Jörg Prante wrote: > If you want to retrieve the term list of an index after Lucene processing > via REST HTTP API, you can try > > [GitHub - jprante/elasticsearch-index-termlist: Elasticsearch Index Termlist](https://github.com/jprante/elasticsearch-index-termlist) > > Jörg > > On Tue, Aug 26, 2014 at 10:41 PM, Kevin B \<[blais...@gmail.com](mailto:blais...@gmail.com) > \\> wrote: > > > Is there any facility in elasticsearch to help with sending terms to an > > external processes after lucene processing (tokenization, filters, etc)? > > The idea here is having some external analysis / nlp code run against the > > documents while keeping all the pre-processing choices consistent and in > > one place (i.e. the analysis setup in elasticsearch index configuration). > > > > I am not very familiar with Lucene, but I believe possibly their update > > request processor is intended for scenarios like this needing a simple > > pipeline. > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/6f60301e-3fe0-4c90-8645-24a18e165a46%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6f60301e-3fe0-4c90-8645-24a18e165a46%40googlegroups.com) > > [https://groups.google.com/d/msgid/elasticsearch/6f60301e-3fe0-4c90-8645-24a18e165a46%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/6f60301e-3fe0-4c90-8645-24a18e165a46%40googlegroups.com?utm_medium=email&utm_source=footer) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/27e2885c-920b-41f1-85c7-6d554fc438c6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/27e2885c-920b-41f1-85c7-6d554fc438c6%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:04am UTC](https://discuss.elastic.co/t/elasticsearch-processing-pipeline-capability/19475/4 "2017-07-06T01:04:02Z")
Closed on July 6, 2017, 1:04am UTC