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

ASF subversion and git services commented on NIFI-6403:
-------------------------------------------------------

Commit 124cdbd3fe5446bff08346e5a28f2883f13e2848 in nifi's branch 
refs/heads/main from Chris Sampson
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=124cdbd ]

NIFI-6403 and NIFI-6404: Elasticsearch 7 support

Addressed PR#4153 comments; removed ES Version property and made Type optional 
in all ES HTTP/Record processors, applying sensible default values where 
required; use _source queyr parameter instead of _source_include/s as it's 
compatible between ES versions

Fix unit test compilation to use JDK8-compatible library/method

Better optional type and id handling for PutElasticsearchRecord; update 
nifi-elasticsearch-client-service build dependencies to use latest versions of 
Elasticsearch in each supported major version (5/6/7); addressed several 
warnings in ElasticSearchClientServiceImpl

This closes #4667.

Signed-off-by: Koji Kawamura <[email protected]>


> 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: Chris Sampson
>            Priority: Major
>         Attachments: NIFI-6403.json, NIFI-6403.xml
>
>   Original Estimate: 0.25h
>          Time Spent: 10h 10m
>  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)

Reply via email to