[
https://issues.apache.org/jira/browse/METRON-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15535949#comment-15535949
]
ASF GitHub Bot commented on METRON-326:
---------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/286
I'd vote for one of two options:
* Investigate how if we can move those interfaces away from `metron-common`
and into `metron-writer` into the `org.apache.metron.writer` package.
* If you can't do above, I'd move `BulkMessageWriter`, `MessageWriter` and
the new response object you've created into `org.apache.metron.common.writer`
> 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)
