[
https://issues.apache.org/jira/browse/NIFI-12255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17844305#comment-17844305
]
ASF subversion and git services commented on NIFI-12255:
--------------------------------------------------------
Commit 9edea70713cd1187d6c699b38a5c2948cd8553a4 in nifi's branch
refs/heads/main from Chris Sampson
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=9edea70713 ]
NIFI-12255 Refactored PutElasticsearchRecord and PutElasticsearchJson
Relationships
- Migrated previous relationship names to be more consistent with other
Processors
- Added nifi-mock objects for Relationship Migration
This closes #7940
Signed-off-by: David Handermann <[email protected]>
> PutElasticsearch* processor relationships should be renamed
> -----------------------------------------------------------
>
> Key: NIFI-12255
> URL: https://issues.apache.org/jira/browse/NIFI-12255
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Chris Sampson
> Assignee: Chris Sampson
> Priority: Minor
> Time Spent: 2h
> Remaining Estimate: 0h
>
> The {{PutElasticsearchRecord}} (and possibly {{PutElasticsearchJson}}) should
> have their relationships renamed to make them clearer for users, for example:
> * failure
> * -original (was success)- - I'm unsure on this
> * successful (i.e. Records that processed in Elasticsearch without error)
> * errors (i.e. Records that resulted in an error within Elasticsearch)
> * error_responses (new for 1.24; the error responses received from
> Elasticsearch, if any)
> The {{Result Record Writer}} should also be made *mandatory* so that
> {{error}} responses from Elasticsearch are always checked and processed to
> send Records to {{successful}} or {{errors}} relationships as appropriate
> (other properties may also want updating/removing to make the UX of these
> processors simpler in this area)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
