You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Chris Sampson (Jira)" <ji...@apache.org> on 2020/11/16 14:03:00 UTC

[jira] [Commented] (NIFI-6403) ElasticSearch field selection broken in Elastic 7.0+

    [ https://issues.apache.org/jira/browse/NIFI-6403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17232782#comment-17232782 ] 

Chris Sampson commented on NIFI-6403:
-------------------------------------

Raised [PR 4667|https://github.com/apache/nifi/pull/4667] to address comments from #4153 and take a slightly different approach.

Attached  [template|^NIFI-6403.xml]/[flow|^NIFI-6403.json] for integration tests with affected processors.

> ElasticSearch field selection broken in Elastic 7.0+
> ----------------------------------------------------
>
>                 Key: NIFI-6403
>                 URL: https://issues.apache.org/jira/browse/NIFI-6403
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.10.0, 1.9.2
>            Reporter: Wietze B
>            Assignee: Joseph Gresock
>            Priority: Major
>         Attachments: NIFI-6403.json, NIFI-6403.xml
>
>   Original Estimate: 0.25h
>          Time Spent: 7h 40m
>  Remaining Estimate: 0h
>
> Elastic has [deprecated|https://www.elastic.co/guide/en/elasticsearch/reference/6.6/breaking-changes-6.6.html#_deprecate_literal__source_exclude_literal_and_literal__source_include_literal_url_parameters] the {{source_include}} search parameter in favour of {{source_includes}} in version 7.0 and higher. 
> This means that processors using the field selection will get an HTTP 400 error upon execution. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)