You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Koji Kawamura (Jira)" <ji...@apache.org> on 2020/05/15 13:29: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=17108282#comment-17108282 ]
Koji Kawamura commented on NIFI-6403:
-------------------------------------
[~jgresock] Thanks for your contribution! Sorry for it's taking so long for your PR to get reviewed. I took a brief look at the latest PR today. And found it covers broader processors to support Elasticsearch 7.x. Would you mind updating this JIRA description to meet the updates?
> 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
> Original Estimate: 0.25h
> Time Spent: 1h 50m
> 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)