[
https://issues.apache.org/jira/browse/NIFI-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16543416#comment-16543416
]
Joseph Gresock commented on NIFI-5427:
--------------------------------------
I have tested this in a live 1.6.0 nifi instance.
> ScrollElasticsearchHttp breaks with Elasticsearch 6
> ---------------------------------------------------
>
> Key: NIFI-5427
> URL: https://issues.apache.org/jira/browse/NIFI-5427
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.4.0, 1.5.0, 1.6.0, 1.7.0
> Reporter: Joseph Gresock
> Assignee: Joseph Gresock
> Priority: Minor
>
> The Elasticsearch 6 Scroll API uses scroll IDs that are nearly 10,000
> characters long. Since the ScrollElasticsearchHttp processor uses a GET
> request for scrolling, this breaks the processor after the first scroll call.
>
> The solution is fairly simple: use a POST instead of a GET for the scroll
> calls. This is backwards compatible down to Elasticsearch 2.X.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
