[jira] [Commented] (SAMZA-427) Serializer and Decoder Interfaces Should Be able to raise Exceptions

["Eli Reisman (JIRA)" <ji...@apache.org>]

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

Eli Reisman commented on SAMZA-427:
-----------------------------------

I was looking for this feature too, glad to see the config option already exists.

Would it be worth considering a list of serdes to be assigned in the job props for a system? Then, as each one failed/threw exception, fall back serde classes could be tried on that message until the list is exhausted and the exception must propagate, or a serde in the chain succeeds?

Example:

systems.whatever.samza.message.serde=json,string,binary



> Serializer and Decoder Interfaces Should Be able to raise Exceptions
> --------------------------------------------------------------------
>
>                 Key: SAMZA-427
>                 URL: https://issues.apache.org/jira/browse/SAMZA-427
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Jonathan Herriott
>              Labels: newbie
>
> Right now, both interfaces expect that an exception cannot be thrown.  The issue I have with this is that if a message is received that cannot be properly decoded (something else wrote a bad message to the same topic) or if implementing an Avro Serde with an Avro Schema Repository Support, which could potentially not even have the schema registered (shouldn't happen, but still need to be able to handle in case it does).



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