[
https://issues.apache.org/jira/browse/NIFI-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17446812#comment-17446812
]
ASF subversion and git services commented on NIFI-1576:
-------------------------------------------------------
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.
> Incorporate feedback/improvements to Elasticsearch processors
> -------------------------------------------------------------
>
> Key: NIFI-1576
> URL: https://issues.apache.org/jira/browse/NIFI-1576
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Matt Burgess
> Priority: Major
>
> Since the release of Apache NiFi 0.5.0 containing FetchElasticsearch and
> PutElasticsearch processors, there have been some improvements identified
> that would add to the usability, flexibility, and power of the Elasticsearch
> processor(s). This Jira should capture those improvements for incorporation
> in a future release.
> Three initial observations:
> 1) FetchElasticsearch currently requires input, but it is possible to
> configure the processor such that no information is required from an incoming
> flow file. The processor should be changed to allow (but not require) input.
> 2) FetchElasticsearch specifies a "Document Identifier" property which may or
> may not contain Expression Language to determine the document ID for
> fetching. However PutElasticsearch only works when the IDs are unique, so it
> specifies a "Identifier Attribute" which forces the user to point at an
> existing attribute. The documentation should be very clear about what the
> properties are and why/how they're used.
> 3) Related to #2, PutElasticsearch's "Identifier Attribute" is required and a
> value for that attribute is currently required. Instead, if no value is
> present, the processor should leverage the auto-generated ID feature of the
> Elasticsearch API.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
