[ https://issues.apache.org/jira/browse/NIFI-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph Percivall reassigned NIFI-5172: -------------------------------------- Assignee: Joseph Percivall > PutElasticSearchRecord does to fail individual recods > ----------------------------------------------------- > > 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 > > 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)