[
https://issues.apache.org/jira/browse/SAMZA-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892612#comment-13892612
]
Chris Riccomini commented on SAMZA-59:
--------------------------------------
This is discussed in some detail in this thread:
http://mail-archives.apache.org/mod_mbox/incubator-samza-dev/201402.mbox/%3ccap1p+ecbd_uvq0w9the2q1eubfdfgky15x79w5+mpnqrvdo...@mail.gmail.com%3E
> 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
>
> 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.1.5#6160)
