[
https://issues.apache.org/jira/browse/KAFKA-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746956#comment-14746956
]
Onur Karaman commented on KAFKA-2409:
-------------------------------------
Is this intended to go into 0.9.0.0? I'm wondering because this requires a
small Consumer API change in the return type from primitive long to object Long:
Before:
{code}
public long committed(TopicPartition partition);
{code}
After:
{code}
public Long committed(TopicPartition partition);
{code}
One consequence of the API change is that it makes the API slightly less
consistent in that position still returns a primitive long.
> 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
>
> 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)
