[
https://issues.apache.org/jira/browse/KAFKA-3203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131805#comment-15131805
]
Grant Henke commented on KAFKA-3203:
------------------------------------
[~becket_qin] I couldn't find anywhere that UnknownMagicByteException was used
or thrown. Perhaps it should just be removed as part of this patch.
I wan't to be careful not to add too many error codes to the map. Would it make
sense to consider a UnknownCodecException as a corrupt message, mapping to
error code 2?
> Add UnknownCodecException and UnknownMagicByteException to error mapping
> ------------------------------------------------------------------------
>
> Key: KAFKA-3203
> URL: https://issues.apache.org/jira/browse/KAFKA-3203
> Project: Kafka
> Issue Type: Bug
> Components: clients, core
> Affects Versions: 0.9.0.0
> Reporter: Jiangjie Qin
> Assignee: Grant Henke
> Fix For: 0.10.0.0, 0.9.1.0
>
>
> Currently most of the exceptions to user have an error code. While
> UnknownCodecException and UnknownMagicByteException can also be thrown to
> client, broker does not have error mapping for them, so clients will only
> receive UnknownServerException, which is vague.
> We should create those two exceptions in client package and add them to error
> mapping.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
