[
https://issues.apache.org/jira/browse/KAFKA-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908302#comment-14908302
]
ASF GitHub Bot commented on KAFKA-2409:
---------------------------------------
GitHub user hachikuji opened a pull request:
https://github.com/apache/kafka/pull/243
KAFKA-2409; have KafkaConsumer.committed return null when there is no commit
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hachikuji/kafka KAFKA-2409
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/243.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #243
----
commit 51d7e0e612731e41c5575bfd4a6efc95807573b4
Author: Jason Gustafson <[email protected]>
Date: 2015-09-25T16:32:24Z
KAFKA-2409; have KafkaConsumer.committed return null when there is no commit
----
> 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: Jason Gustafson
> 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)
