# JEST Client for Elastic Search 5.6 or Java Rest client for ES 5.6 **URL:** \ **Category:** Elasticsearch\ **Created:** [October 5, 2017, 8:48pm UTC](https://discuss.elastic.co/t/jest-client-for-elastic-search-5-6-or-java-rest-client-for-es-5-6/102910 "2017-10-05T20:48:42Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![kasi](https://avatars.discourse-cdn.com/v4/letter/k/e19b73/32.png) [@kasi](https://discuss.elastic.co/u/kasi)\ **Post date:** [October 5, 2017, 8:48pm UTC](https://discuss.elastic.co/t/jest-client-for-elastic-search-5-6-or-java-rest-client-for-es-5-6/102910/1 "2017-10-05T20:48:42Z")
What would be the compelling reason to move from JEST Client to using Java Rest client for ES 5.6 ? The way I see it JEST client offers a better wrapper for admin calls to manage index templates. Thanks, Kasi ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [October 5, 2017, 11:54pm UTC](https://discuss.elastic.co/t/jest-client-for-elastic-search-5-6-or-java-rest-client-for-es-5-6/102910/2 "2017-10-05T23:54:36Z")
> [@kasi](#): > > What would be the compelling reason to move from JEST Client to using Java Rest client for ES 5.6 ? We're fully backing the REST client, and will be releasing new versions when new versions of Elasticsearch lands. So there's no wait between a new Elasticsearch version and a client update. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 2, 2017, 11:55pm UTC](https://discuss.elastic.co/t/jest-client-for-elastic-search-5-6-or-java-rest-client-for-es-5-6/102910/3 "2017-11-02T23:55:14Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.