# Official Python client vs PyES **URL:** \ **Category:** Elasticsearch\ **Created:** [October 24, 2013, 9:00am UTC](https://discuss.elastic.co/t/official-python-client-vs-pyes/14086 "2013-10-24T09:00:56Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![haizaar](https://avatars.discourse-cdn.com/v4/letter/h/3d9bf3/32.png) [@haizaar](https://discuss.elastic.co/u/haizaar)\ **Post date:** [October 24, 2013, 9:00am UTC](https://discuss.elastic.co/t/official-python-client-vs-pyes/14086/1 "2013-10-24T09:00:56Z")
Good day, I've noticed that official Python client[http://elasticsearch-py.readthedocs.org/en/latest/](http://elasticsearch-py.readthedocs.org/en/latest/)for Elastic Search was announced some time ago. Till now I was using PyES [https://github.com/aparo/pyes](https://github.com/aparo/pyes) and was pretty happy with it. Quick looking at the new clients, the API looks very similar to PyES, however the code does not. So I have a couple of questions: 1. ES developers - why did you decide to start a new project and not to "adopt" PyES. 2. Community - which client do you prefer and why? Thanks, Zaar -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Honza\_Kral](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/honza_kral/32/876_2.png) [@Honza\_Kral](https://discuss.elastic.co/u/Honza_Kral)\ **Post date:** [October 24, 2013, 11:40am UTC](https://discuss.elastic.co/t/official-python-client-vs-pyes/14086/2 "2013-10-24T11:40:16Z")
Hello Zaar, Our decision to create our own clients was mostly about consistency for our users. To do that we created a set of low-level clients that map very closely to the REST api. We made sure (and are continuously doing so) that these clients implement all the API endpoints as well as all parameters and to the right thing. We tried our best to avoid any design decisions in those clients to make sure everybody could use them, even if it means creating their own abstraction on top of it. The overhead of the clients are so small and their design flexible enough (we hope) that all the other clients can live on top of these. I hope that answers your first question. For more information I'll be doing a webinar about this - why we chose to do the clients, what drove the design decisions we took and what is the future of the python client(s). It should take place next week sometime. Thanks! Honza Král Python developer for Elasticsearch On Thu, Oct 24, 2013 at 11:00 AM, Zaar Hai [haizaar@gmail.com](mailto:haizaar@gmail.com) wrote: > Good day, > > I've noticed that official Python client[http://elasticsearch-py.readthedocs.org/en/latest/](http://elasticsearch-py.readthedocs.org/en/latest/)for Elastic Search was announced some time ago. > Till now I was using PyES [https://github.com/aparo/pyes](https://github.com/aparo/pyes) and was pretty > happy with it. > > Quick looking at the new clients, the API looks very similar to PyES, > however the code does not. > > So I have a couple of questions: > > 1. ES developers - why did you decide to start a new project and not to > "adopt" PyES. > 2. Community - which client do you prefer and why? > > Thanks, > Zaar > > -- > 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). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![haizaar](https://avatars.discourse-cdn.com/v4/letter/h/3d9bf3/32.png) [@haizaar](https://discuss.elastic.co/u/haizaar)\ **Post date:** [October 24, 2013, 11:58am UTC](https://discuss.elastic.co/t/official-python-client-vs-pyes/14086/3 "2013-10-24T11:58:13Z")
Hi Honza, Thanks for the explanation. It makes sense. Where can I find more info about this webinar? Zaar On Thursday, October 24, 2013 2:40:16 PM UTC+3, Honza Král wrote: > Hello Zaar, > > Our decision to create our own clients was mostly about consistency for > our users. To do that we created a set of low-level clients that map very > closely to the REST api. We made sure (and are continuously doing so) that > these clients implement all the API endpoints as well as all parameters and > to the right thing. > > We tried our best to avoid any design decisions in those clients to make > sure everybody could use them, even if it means creating their own > abstraction on top of it. The overhead of the clients are so small and > their design flexible enough (we hope) that all the other clients can live > on top of these. > > I hope that answers your first question. For more information I'll be > doing a webinar about this - why we chose to do the clients, what drove the > design decisions we took and what is the future of the python client(s). It > should take place next week sometime. > > Thanks! > > Honza Král > Python developer for Elasticsearch > > On Thu, Oct 24, 2013 at 11:00 AM, Zaar Hai \<[hai...@gmail.com](mailto:hai...@gmail.com) \ > > > wrote: > > > Good day, > > > > I've noticed that official Python client[http://elasticsearch-py.readthedocs.org/en/latest/](http://elasticsearch-py.readthedocs.org/en/latest/)for Elastic Search was announced some time ago. > > Till now I was using PyES [https://github.com/aparo/pyes](https://github.com/aparo/pyes) and was pretty > > happy with it. > > > > Quick looking at the new clients, the API looks very similar to PyES, > > however the code does not. > > > > So I have a couple of questions: > > > > 1. ES developers - why did you decide to start a new project and not to > > "adopt" PyES. > > 2. Community - which client do you prefer and why? > > > > Thanks, > > Zaar > > > > -- > > 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) \. > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Honza\_Kral](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/honza_kral/32/876_2.png) [@Honza\_Kral](https://discuss.elastic.co/u/Honza_Kral)\ **Post date:** [October 27, 2013, 2:04pm UTC](https://discuss.elastic.co/t/official-python-client-vs-pyes/14086/4 "2013-10-27T14:04:14Z")
The info is now out: > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. On Thu, Oct 24, 2013 at 1:58 PM, Zaar Hai [haizaar@gmail.com](mailto:haizaar@gmail.com) wrote: > Hi Honza, > > Thanks for the explanation. It makes sense. > Where can I find more info about this webinar? > > Zaar > > On Thursday, October 24, 2013 2:40:16 PM UTC+3, Honza Král wrote: > > > Hello Zaar, > > > > Our decision to create our own clients was mostly about consistency for > > our users. To do that we created a set of low-level clients that map very > > closely to the REST api. We made sure (and are continuously doing so) that > > these clients implement all the API endpoints as well as all parameters and > > to the right thing. > > > > We tried our best to avoid any design decisions in those clients to make > > sure everybody could use them, even if it means creating their own > > abstraction on top of it. The overhead of the clients are so small and > > their design flexible enough (we hope) that all the other clients can live > > on top of these. > > > > I hope that answers your first question. For more information I'll be > > doing a webinar about this - why we chose to do the clients, what drove the > > design decisions we took and what is the future of the python client(s). It > > should take place next week sometime. > > > > Thanks! > > > > Honza Král > > Python developer for Elasticsearch > > > > On Thu, Oct 24, 2013 at 11:00 AM, Zaar Hai [hai...@gmail.com](mailto:hai...@gmail.com) wrote: > > > > > Good day, > > > > > > I've noticed that official Python client[http://elasticsearch-py.readthedocs.org/en/latest/](http://elasticsearch-py.readthedocs.org/en/latest/)for Elastic Search was announced some time ago. > > > Till now I was using PyES [https://github.com/aparo/pyes](https://github.com/aparo/pyes) and was > > > pretty happy with it. > > > > > > Quick looking at the new clients, the API looks very similar to PyES, > > > however the code does not. > > > > > > So I have a couple of questions: > > > > > > 1. ES developers - why did you decide to start a new project and not to > > > "adopt" PyES. > > > 2. Community - which client do you prefer and why? > > > > > > Thanks, > > > Zaar > > > > > > -- > > > 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](http://googlegroups.com). > > > > > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out) > > > . > > > > -- > > 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). > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:10am UTC](https://discuss.elastic.co/t/official-python-client-vs-pyes/14086/5 "2017-07-06T02:10:25Z")