[
https://issues.apache.org/jira/browse/NIFI-9439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453673#comment-17453673
]
ASF subversion and git services commented on NIFI-9439:
-------------------------------------------------------
Commit 53809dd83f1b2e150aaf70a607f6885fa292cbdd in nifi's branch
refs/heads/main from Chris Sampson
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=53809dd ]
NIFI-9439:
- Add PutElasticsearchJson processor to Elasticsearch REST bundle
- Deprecate PutElasticsearchHttp/PutElasticsearchHttpReccord in favour of
Elasticsearch REST processors
Signed-off-by: Joe Gresock <[email protected]>
This closes #5566.
> Create an Elasticsearch REST processor to send the entire JSON content of a
> FlowFile to Elasticsearch
> -----------------------------------------------------------------------------------------------------
>
> Key: NIFI-9439
> URL: https://issues.apache.org/jira/browse/NIFI-9439
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Chris Sampson
> Assignee: Chris Sampson
> Priority: Major
> Attachments: NIFI-9439.json
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> The Elasticsearch REST Processor bundle should contain the equivalent of the
> existing {{PutElasticsearchHttp}} procressor, which sends the entire JSON
> contents of a FlowFile to Elasticsearch as part ofa {{_bulk}} operation.
> Adding the equivalent capability to the ES REST bundle means it can then
> replace all the functionality previously implemented in older Elasticsearch
> processor bundles.
> The advantage of the ES REST bundle is its use of the official Elasticsearch
> REST API client libraries and the ability to switch that out for other
> implementations in the future (e.g. AWS OpenSearch client libraries).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
