# Erlang Client **URL:** \ **Category:** Elasticsearch\ **Created:** [March 8, 2010, 5:16pm UTC](https://discuss.elastic.co/t/erlang-client/2839 "2010-03-08T17:16:05Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![kungfooguru](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kungfooguru/32/3298_2.png) [@kungfooguru](https://discuss.elastic.co/u/kungfooguru)\ **Post date:** [March 8, 2010, 5:16pm UTC](https://discuss.elastic.co/t/erlang-client/2839/1 "2010-03-08T17:16:05Z")
If anyone is interested I have started an Erlang client for Elastic Search: [http://github.com/kungfooguru/erlastic\_search](http://github.com/kungfooguru/erlastic_search) Elastic Search is amazing for using with CouchDB 🙂 Tristan ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [March 9, 2010, 11:40am UTC](https://discuss.elastic.co/t/erlang-client/2839/2 "2010-03-09T11:40:59Z")
This is really cool!. Can you share your thoughts on integrating it with couchdb? One thing that I thought about is doing something similar to what couchdb-lucene does, which, if I understand correctly, simply polls a view for its changes and applies them to Lucene. This, of course, can be really simple with elasticsearch. -shay.banon On Mon, Mar 8, 2010 at 7:16 PM, kungfooguru [kungfooguru@gmail.com](mailto:kungfooguru@gmail.com) wrote: > If anyone is interested I have started an Erlang client for Elastic > Search: [http://github.com/kungfooguru/erlastic\_search](http://github.com/kungfooguru/erlastic_search) > > Elastic Search is amazing for using with CouchDB 🙂 > > Tristan ---
**Author:** ![kungfooguru](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kungfooguru/32/3298_2.png) [@kungfooguru](https://discuss.elastic.co/u/kungfooguru)\ **Post date:** [March 9, 2010, 2:20pm UTC](https://discuss.elastic.co/t/erlang-client/2839/3 "2010-03-09T14:20:24Z")
My initial thoughts were to do something like that or to integrate it through the updates attribute: [http://wiki.apache.org/couchdb/How\_to\_intercept\_document\_updates\_and\_perform\_additional\_server-side\_processing](http://wiki.apache.org/couchdb/How_to_intercept_document_updates_and_perform_additional_server-side_processing) The documentation on these features is lacking though... And javascript can frustrate me easily, hehe. So for my project I'll simply be using Couchbeam and my Elastic Search Erlang client together. This requires logic to be able to roll back if one works and the other doesn't of course, and maybe the updates attribute makes that easier, I'd hope it does. So I'd think ultimately server side processing to push it to Elastic Search would be best. I'm not sure if the Lucene integration will be moving to something like that... If not I could be wrong :). Tristan On Tue, Mar 9, 2010 at 5:40 AM, Shay Banon [shay.banon@elasticsearch.com](mailto:shay.banon@elasticsearch.com)wrote: > This is really cool!. Can you share your thoughts on integrating it with > couchdb? One thing that I thought about is doing something similar to what > couchdb-lucene does, which, if I understand correctly, simply polls a view > for its changes and applies them to Lucene. This, of course, can be really > simple with elasticsearch. > > -shay.banon > > On Mon, Mar 8, 2010 at 7:16 PM, kungfooguru [kungfooguru@gmail.com](mailto:kungfooguru@gmail.com) wrote: > > > If anyone is interested I have started an Erlang client for Elastic > > Search: [http://github.com/kungfooguru/erlastic\_search](http://github.com/kungfooguru/erlastic_search) > > > > Elastic Search is amazing for using with CouchDB 🙂 > > > > Tristan ---
**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, 4:25am UTC](https://discuss.elastic.co/t/erlang-client/2839/4 "2017-07-06T04:25:23Z")