[NIFI-4002] Add PutElasticsearchHttpRecord processor

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.3.0
• Component/s: Extensions
• Assignee: Matt Burgess
• Reporter: Matt Burgess
• Created: 01/Jun/17 12:52
• Updated: 02/Jun/17 17:29
• Resolved: 02/Jun/17 17:29

Description

With the new Record Reader/Writer capabilities, and that the PutElasticsearch processors only handle a single document at a time, it would be nice to have a "record-aware" PutES processor, where the user could specify a Record Reader and for each record in the input, the processor would convert the record to JSON and push to an ES cluster. One necessary (but optional) property would be a Record Path to a field/value to be used as the document identifier (the current PutES processors require an attribute to hold the identifier). If the Record Path is not set and the operation is "index", then just like the PutES processors, the document identifier will be autogenerated.

Issue Links

• links to: GitHub Pull Request #1878