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

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

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

- NIFI-9388: add GetElasticsearch to fetch Elasticsearch document using the 
ElasticsearchClientService
- NIFI-9387: add Proxy capability to ElasticsearchClientService
- NIFI-1576: allow GetElasticsearch to run without requiring FlowFile input

Signed-off-by: Joe Gresock <[email protected]>

This closes #5535.


> Elasticsearch processor to fetch a single document by _id using the 
> ElasticsearchClientService
> ----------------------------------------------------------------------------------------------
>
>                 Key: NIFI-9388
>                 URL: https://issues.apache.org/jira/browse/NIFI-9388
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 1.15.0
>            Reporter: Chris Sampson
>            Assignee: Chris Sampson
>            Priority: Minor
>         Attachments: get_elasticsearch.json
>
>          Time Spent: 4h 40m
>  Remaining Estimate: 0h
>
> An equivalent processor to the existing 
> {{FetchElasticsearch}}/{{FetchElasticsearchHttp}} processors should be 
> created that uses the {{ElasticsearchClientService}} (and thus the official 
> Elastic connection libraries).
> Consider also allowing the GET of an Elasticsearch document with the new 
> processor without the need for an input FlowFile (i.e. allow the processor to 
> be run as a "source" processor for the start of a Flow with the {{Document 
> Identifier}} being provided by the processor property)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to