[
https://issues.apache.org/jira/browse/KAFKA-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361868#comment-14361868
]
Jay Kreps commented on KAFKA-2020:
----------------------------------
Is this the case where we are sending back an error code but ALSO sending back
data and the error code doesn't mean that there is an error but just means "hey
I wanted to tell you something in the response so i filled in an error,
hopefully you didn't handle that error like every single other error and throw
an exception"?
> I expect ReplicaNotAvailableException to have proper Javadocs
> -------------------------------------------------------------
>
> Key: KAFKA-2020
> URL: https://issues.apache.org/jira/browse/KAFKA-2020
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Reporter: Chris Riccomini
> Assignee: Neha Narkhede
>
> It looks like ReplicaNotAvailableException was copy and pasted from
> LeaderNotAvailable exception. The Javadocs were never changed. This means
> that users think that ReplicaNotAvailableException signifies leaders are not
> available. This is very different from, "I can ignore this exception," which
> is what the Kafka protocol docs say to do with ReplicaNotAvailableException.
> Related: what's the point of ReplicaNotAvailableException if it's supposed to
> be ignored?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
