[
https://issues.apache.org/jira/browse/KAFKA-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172513#comment-14172513
]
Ewen Cheslack-Postava commented on KAFKA-1637:
----------------------------------------------
Updated reviewboard https://reviews.apache.org/r/26710/diff/
against branch origin/trunk
> SimpleConsumer.fetchOffset returns wrong error code when no offset exists for
> topic/partition/consumer group
> ------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-1637
> URL: https://issues.apache.org/jira/browse/KAFKA-1637
> Project: Kafka
> Issue Type: Bug
> Components: consumer, core
> Affects Versions: 0.8.1, 0.8.1.1
> Environment: Linux
> Reporter: Amir Malekpour
> Assignee: Ewen Cheslack-Postava
> Labels: newbie
> Attachments: KAFKA-1637.patch, KAFKA-1637_2014-10-15_09:08:12.patch
>
>
> This concerns Kafka's Offset Fetch API:
> According to Kafka's current documentation, "if there is no offset associated
> with a topic-partition under that consumer group the broker does not set an
> error code (since it is not really an error), but returns empty metadata and
> sets the offset field to -1." (Link below)
> However, in Kafka 08.1.1 Error code '3' is returned, which effectively makes
> it impossible for the client to decide if there was an error, or if there is
> no offset associated with a topic-partition under that consumer group.
> https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol#AGuideToTheKafkaProtocol-MetadataAPI
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
