[NIFI-9581] PutElasticsearchRecord should make it easier for users to distinguish between Records that resulted in Elasticsearch errors and those that did not

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.14.0
• Fix Version/s: 1.16.0
• Assignee: Chris Sampson
• Reporter: Chris Sampson
• Created: 17/Jan/22 21:08
• Updated: 17/Oct/22 13:26
• Resolved: 22/Feb/22 16:43

Description

The PutElasticsearchRecord processor will currently optionally log Records from the input FlowFile that were marked as resulting in an error within Elasticsearch; these same Records can optionally be directed to the errors Relationship from the Processor if the user provides an appropriate Error Record Writer.

The original input FlowFile is always sent to the success Relationship irrespective of whether any/all Records resulted in Elasticsearch errors (unless the call to Elasticsearch itself fails, in which case the FlowFile is routed to failure or retry depending upon the Exception type).

It would be more useful if the Records that did not result in errors were also written to a Relationship such that users could process those separate to the errored Records without having to try and find them from the original input. This would more closely mirror what is already done as part of the PutElasticsearchHttpRecord processor, which separates Records between the success and failed Relationships depending upon the Elasticsearch responses for each Record.

Issue Links

• fixes: NIFI-5982 Processor PutElasticsearchHttpRecord should a relation Response
• links to: GitHub Pull Request #5665