[
https://issues.apache.org/jira/browse/KAFKA-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905364#comment-14905364
]
Onur Karaman commented on KAFKA-2409:
-------------------------------------
Yeah I think KAFKA-2403's change to have OffsetAndMetadata for committed() and
long for position() makes more sense than the ticket's originally proposed Long
for committed() and long for position()
> Have KafkaConsumer.committed() return null when there is no committed offset
> ----------------------------------------------------------------------------
>
> Key: KAFKA-2409
> URL: https://issues.apache.org/jira/browse/KAFKA-2409
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Jason Gustafson
> Assignee: Sreepathi Prasanna
> Priority: Minor
> Labels: newbie
> Fix For: 0.9.0.0
>
>
> Currently checking whether an offset has been committed requires catching
> NoOffsetForPartitionException. Since this is likely a fairly common case, it
> is more convenient for users just to return null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
