[
https://issues.apache.org/jira/browse/SAMZA-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14155154#comment-14155154
]
Chris Riccomini commented on SAMZA-427:
---------------------------------------
Thus far, we've just been doing everything with unchecked exceptions.
Personally, I'm strongly averse to checked exceptions.
What we'd have to end up adding would most likely be "throws Exception". This
doesn't seem much different than just throwing an unchecked exception to me.
Also, I think this change would be backwards incompatible, since implemented
serdes will have to update to "throws Exception".
My personal vote would be to leave it as is, and throw unchecked exceptions.
> 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
> Fix For: 0.8.0
>
>
> 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)
