# \[BUG\] You can use BulkProcessor with high-level client in 5.6 version

**URL:** <https://discuss.elastic.co/t/bug-you-can-use-bulkprocessor-with-high-level-client-in-5-6-version/123602>\
**Category:** Elasticsearch\
**Created:** [March 12, 2018, 5:31pm UTC](https://discuss.elastic.co/t/bug-you-can-use-bulkprocessor-with-high-level-client-in-5-6-version/123602 "2018-03-12T17:31:22Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![juanaramis](https://avatars.discourse-cdn.com/v4/letter/j/a6a055/32.png) [@juanaramis](https://discuss.elastic.co/u/juanaramis)\
**Post date:** [March 12, 2018, 5:31pm UTC](https://discuss.elastic.co/t/bug-you-can-use-bulkprocessor-with-high-level-client-in-5-6-version/123602/1 "2018-03-12T17:31:22Z")

</div>

Hi team,

Thanks in advance

I try to create a BulkProcessor like  
[https://www.elastic.co/guide/en/elasticsearch/client/java-rest/5.6/java-rest-high-document-bulk.html](https://www.elastic.co/guide/en/elasticsearch/client/java-rest/5.6/java-rest-high-document-bulk.html)

with the high-level client in the version 5.6 but I get this compilation error at this point:  
...  
RestHighLevelClient rHLClient  
...  
BulkProcessor bulkProcessor = BulkProcessor.builder( **rHLClient::bulkAsync** , listener,threadPool).build();

"Client is not a functional interface"

If there is a better way to use that, please advise. I've been blocked on it.

Thanks

J.

---

<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:** [March 12, 2018, 7:36pm UTC](https://discuss.elastic.co/t/bug-you-can-use-bulkprocessor-with-high-level-client-in-5-6-version/123602/2 "2018-03-12T19:36:18Z")

</div>

Not sure.

It looks correct to me.  
May be share a sample project?

At least on 6.2, I don't have this issue.

Strange that there is a mention of `Client` which you don't have in your code.

---

<div class="post-metadata">

**Author:** ![juanaramis](https://avatars.discourse-cdn.com/v4/letter/j/a6a055/32.png) [@juanaramis](https://discuss.elastic.co/u/juanaramis)\
**Post date:** [March 12, 2018, 8:11pm UTC](https://discuss.elastic.co/t/bug-you-can-use-bulkprocessor-with-high-level-client-in-5-6-version/123602/3 "2018-03-12T20:11:06Z")

</div>

Hi,  
Thanks David,

I have to use 5.6 version. Do you know what kind of problem can produce this error?  
In my search I found this:

> <https://stackoverflow.com/questions/47683320/resthighlevelclient-with-bulkprocessor-elastic-search-issue>

Can you share an example with the 5.6 version?

Thanks in advance,

J.

---

<div class="post-metadata">

**Author:** ![juanaramis](https://avatars.discourse-cdn.com/v4/letter/j/a6a055/32.png) [@juanaramis](https://discuss.elastic.co/u/juanaramis)\
**Post date:** [March 13, 2018, 8:11pm UTC](https://discuss.elastic.co/t/bug-you-can-use-bulkprocessor-with-high-level-client-in-5-6-version/123602/4 "2018-03-13T20:11:01Z")

</div>

I think this is a BUG  
Please, any help with this will be welcome

thanks

---

<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:** [March 13, 2018, 8:35pm UTC](https://discuss.elastic.co/t/bug-you-can-use-bulkprocessor-with-high-level-client-in-5-6-version/123602/5 "2018-03-13T20:35:57Z")

</div>

As I said:

> [@dadoonet](#):
>
> May be share a sample project?

---

<div class="post-metadata">

**Author:** ![juanaramis](https://avatars.discourse-cdn.com/v4/letter/j/a6a055/32.png) [@juanaramis](https://discuss.elastic.co/u/juanaramis)\
**Post date:** [March 14, 2018, 2:38pm UTC](https://discuss.elastic.co/t/bug-you-can-use-bulkprocessor-with-high-level-client-in-5-6-version/123602/6 "2018-03-14T14:38:58Z")

</div>

Hi David, thanks

I'm using internal repositories and specific gradle configuration. I saw a code you shared but it was under 6.x version.

thanks in advance

J.

---

<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:** [March 14, 2018, 4:02pm UTC](https://discuss.elastic.co/t/bug-you-can-use-bulkprocessor-with-high-level-client-in-5-6-version/123602/7 "2018-03-14T16:02:56Z")

</div>

I can't help if I can't reproduce the problem I'm afraid.

---

<div class="post-metadata">

**Author:** ![juanaramis](https://avatars.discourse-cdn.com/v4/letter/j/a6a055/32.png) [@juanaramis](https://discuss.elastic.co/u/juanaramis)\
**Post date:** [March 14, 2018, 4:11pm UTC](https://discuss.elastic.co/t/bug-you-can-use-bulkprocessor-with-high-level-client-in-5-6-version/123602/9 "2018-03-14T16:11:41Z")

</div>

Thank you David

As I said: It was a bug, but not from elastic for sure

[https://bugs.eclipse.org/bugs/show\_bug.cgi?id=514884](https://bugs.eclipse.org/bugs/show_bug.cgi?id=514884)

interesting...

Thank you for your answers and patience

J.

---

<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:** [March 14, 2018, 4:13pm UTC](https://discuss.elastic.co/t/bug-you-can-use-bulkprocessor-with-high-level-client-in-5-6-version/123602/10 "2018-03-14T16:13:48Z")

</div>

Ha great!

I was confused by:

> thanks in advance

And I thought you were waiting for something from my side.

Happy it's "solved" now.

---

<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:** [April 11, 2018, 4:13pm UTC](https://discuss.elastic.co/t/bug-you-can-use-bulkprocessor-with-high-level-client-in-5-6-version/123602/11 "2018-04-11T16:13:49Z")

</div>

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