[
https://issues.apache.org/jira/browse/NIFI-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777334#comment-16777334
]
ASF subversion and git services commented on NIFI-5172:
-------------------------------------------------------
Commit cd7edb1c04fdd977de1fa30d1dbe4bf93c4afda2 in nifi's branch
refs/heads/master from Joe Percivall
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=cd7edb1 ]
NIFI-5172 Adding the ability to specify a record writer for
PutElasticsearchHttpRecord in order to individually handle failed records
Addressing PR feedback
Signed-off-by: Matthew Burgess <[email protected]>
This closes #3299
> PutElasticsearchHttpRecord does not handle failed records individually
> ----------------------------------------------------------------------
>
> Key: NIFI-5172
> URL: https://issues.apache.org/jira/browse/NIFI-5172
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.6.0
> Reporter: Juan C. Sequeiros
> Assignee: Joseph Percivall
> Priority: Minor
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> My observation and not sure if working as expected but when I send my output
> from MergeRecord ( set to 10000 ) max number of records and one of those
> records has an invalid timestamp "bogusdata" value ES rejects it, rightly so
> since on ES we have a schema template more granular and is expecting
> timestamp as type "date".
>
> From USER forums Matt Burgess:
> Yes the current behavior is to move the entire input flowfile to
> failure if any errors occur. Some other record-aware processors create
> separate flow files for failed and successful records, but
> PutElasticsearchHttpRecord does not (yet) do that. Please feel free to
> write a Jira for this improvement.
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
