[
https://issues.apache.org/jira/browse/SAMZA-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157200#comment-14157200
]
Yan Fang commented on SAMZA-427:
--------------------------------
{quote}
I guess the feature I'd like out of this is the ability to say "skip this
message on failure"
{quote}
This feature has been added to the master branch, with a property,
[task.drop.deserialization.errors|http://samza.incubator.apache.org/learn/documentation/latest/jobs/configuration-table.html]
. See SAMZA-59 . What it does is to skip this message, record the exceptions
in the log file and add +1 in a metric counter, called "deserialization error".
> 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)
