You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Yan Fang (JIRA)" <ji...@apache.org> on 2014/07/02 19:01:30 UTC
[jira] [Updated] (SAMZA-59) Support dropping messages on serde
failures
[ https://issues.apache.org/jira/browse/SAMZA-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yan Fang updated SAMZA-59:
--------------------------
Attachment: SAMZA-59.patch
RB: https://reviews.apache.org/r/23235/
Added a "task.drop.deserialization.errors" property to support this feature. More detail is in RB description part. Thank you.
> Support dropping messages on serde failures
> -------------------------------------------
>
> Key: SAMZA-59
> URL: https://issues.apache.org/jira/browse/SAMZA-59
> Project: Samza
> Issue Type: Bug
> Components: container
> Reporter: Chris Riccomini
> Assignee: Yan Fang
> Attachments: SAMZA-59.patch
>
>
> Samza uses the Serde interface to serialize and deserialize messages when producing and sending them.
> Right now, if a Serde is unable to (de)serialize a message, it has no choice but to throw an exception, or put some non-standard surrogate object in the message envelope's key/value fields. If an exception is throws, the whole container fails.
> We should make it possible for Serdes to signal to Samza that they were unable to (de)serialize the message in question, and add configuration to Samza to be able to drop these messages rather than throwing an exception.
--
This message was sent by Atlassian JIRA
(v6.2#6252)