# Questions Migrating to Java High Level Rest Client 5.6

**URL:** <https://discuss.elastic.co/t/questions-migrating-to-java-high-level-rest-client-5-6/101677>\
**Category:** Elasticsearch\
**Created:** [September 25, 2017, 10:16am UTC](https://discuss.elastic.co/t/questions-migrating-to-java-high-level-rest-client-5-6/101677 "2017-09-25T10:16:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Herm\_Flink](https://avatars.discourse-cdn.com/v4/letter/h/6de8d8/32.png) [@Herm\_Flink](https://discuss.elastic.co/u/Herm_Flink)\
**Post date:** [September 25, 2017, 10:16am UTC](https://discuss.elastic.co/t/questions-migrating-to-java-high-level-rest-client-5-6/101677/1 "2017-09-25T10:16:10Z")

</div>

Hi All,

At the moment, we are investigating efforts to move away from the Java Transport Client to the new Java High Level Rest Client.

Two questions already popped up:

1. For the BulkProcessor we now need to make use of the ThreadPool class. See example in [https://www.elastic.co/guide/en/elasticsearch/client/java-rest/5.6/java-rest-high-document-bulk.html#java-rest-high-document-bulk-processor](https://www.elastic.co/guide/en/elasticsearch/client/java-rest/5.6/java-rest-high-document-bulk.html#java-rest-high-document-bulk-processor). However, I do not see any documentation explaining the Settings objects that is required for the ThreadPool constructor. Can someone please explain me what is required to instantiate a valid Settings object for ThreadPool? (we are using ES Found, should that matter)
2. According same documentation, the Mapping API still requires the Low-level Rest Client. This is a cumbersome Client to code against. The code we probably need to modify again once it is supported by the High Level Client. Can someone shed a light on the roadmap when the Mapping API becomes available in the High Level Rest Client?

Many thanks in advance for responding, kind regards,  
Herm Flink

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [September 25, 2017, 11:02am UTC](https://discuss.elastic.co/t/questions-migrating-to-java-high-level-rest-client-5-6/101677/2 "2017-09-25T11:02:42Z")

</div>

Read this:

> <https://github.com/elastic/elasticsearch/issues/26028>

Basically:

```auto
ThreadPool threadPool = new ThreadPool(Settings.builder()
    .put(Node.NODE_NAME_SETTING.getKey(), "high-level-client")
    .build());

```

And also

> <https://github.com/elastic/elasticsearch/issues/25847>

---

<div class="post-metadata">

**Author:** ![Herm\_Flink](https://avatars.discourse-cdn.com/v4/letter/h/6de8d8/32.png) [@Herm\_Flink](https://discuss.elastic.co/u/Herm_Flink)\
**Post date:** [September 25, 2017, 11:30am UTC](https://discuss.elastic.co/t/questions-migrating-to-java-high-level-rest-client-5-6/101677/3 "2017-09-25T11:30:54Z")

</div>

Ah, great! Thanks for pointing me to the right directions.  
Guess I'll have to deal with the low level client for indices admin (and mappings) for now... and wait for [https://github.com/elastic/elasticsearch/issues/25847](https://github.com/elastic/elasticsearch/issues/25847) to be resolved in some future release.

---

<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:** [October 23, 2017, 11:30am UTC](https://discuss.elastic.co/t/questions-migrating-to-java-high-level-rest-client-5-6/101677/4 "2017-10-23T11:30:58Z")

</div>

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