[jira] [Commented] (KAFKA-2020) I expect ReplicaNotAvailableException to have proper Javadocs

["Chris Riccomini (JIRA)" <ji...@apache.org>]

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

Chris Riccomini commented on KAFKA-2020:
----------------------------------------

Also related, we're using ErrorMapping.maybeThrowException in our Kafka consumer. Apparently Kafka isn't even using this, except in tests. Are we supposed to use this method or not?

> 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)