[jira] [Commented] (METRON-326) Error Handling in ElasticsearchWriter

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/METRON-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542336#comment-15542336 ] 

ASF GitHub Bot commented on METRON-326:
---------------------------------------

Github user justinleet commented on the issue:

    https://github.com/apache/incubator-metron/pull/286
  
    Moving everything to `metron-writer` seems to cause random build failures (e.g. the one above), based on how things get spun up.  It is not deterministic.  I'm going to try using option 2, and try testing that and seeing if it's consistent.


> Error Handling in ElasticsearchWriter
> -------------------------------------
>
>                 Key: METRON-326
>                 URL: https://issues.apache.org/jira/browse/METRON-326
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Ajay Yadav
>            Assignee: Justin Leet
>
> In Elasticsearch writer we raise a exception if BulkResponse object has failures and that results in failing the whole batch even if some objects failed in it. This has spiral effect specially when there is continuous stream of bad messages and errorStream is tied to indexingBolt. 
> If possible we should iterate through items in BulkResponse object and send only failed messages to errorStream.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)