kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "kambiz shahri (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (KAFKA-3824) Docs indicate auto.commit breaks at least once delivery but that is incorrect
Date Wed, 22 Jun 2016 07:50:57 GMT

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

kambiz shahri edited comment on KAFKA-3824 at 6/22/16 7:50 AM:
---------------------------------------------------------------

My gripe is 3 fold:
1. The reporter of the issue simply did not bother to reply 
2. It is as clear as mud
3. We all should have a chance to understand who has done what to the Consumer with regards
to autocommit and how it affects least once delivery; there are production systems running
out there, that might be adversely affected, by a subtlety that someone is not bothered to
document or even reply to a request for clarification.

Internal or external, there should be clarity on such an important class.

Also, farming out JavaDoc or Documentation to a Newbie, who then does her/his due-diligence,
and requests clarification, which means the reporter has to do more work, and then just reassigns
it, because he cannot be bothered to explain changes he made, is a very poor reflection on
Kafka.

So please, related or not, all changes to the Consumer should be made clear, and explained
so it can be documented.
Assigning it back to myself, to be fobbed off more, is not of interest.


was (Author: beez):
My gripe is 3 fold:
1. The reporter of the issue simply did not bother to reply 
2. It is as clear as mud
3. We all should have a chance to understand who has done what to the Consumer with regards
to autocommit and how it affects least once delivery; there are production systems running
out there, that might be adversely affected, by a subtlety that someone is not bothered to
document or even reply to a request for a clarification.

Internal or external, there should be clarity on such an important class.

Also, farming out JavaDoc or Documentation to a Newbie, who then does her/his due-diligence,
and requests clarification, which means the reporter has to do more work, and then just reassigns
it, because he cannot be bothered to explain changes he made, is a very poor reflection on
Kafka.

So please, related or not, all changes to the Consumer should be made clear, and explained
so it can be documented.
Assigning it back to myself, to be fobbed off more, is not of interest.

> Docs indicate auto.commit breaks at least once delivery but that is incorrect
> -----------------------------------------------------------------------------
>
>                 Key: KAFKA-3824
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3824
>             Project: Kafka
>          Issue Type: Improvement
>          Components: consumer
>    Affects Versions: 0.10.0.0
>            Reporter: Jay Kreps
>            Assignee: Jason Gustafson
>              Labels: newbie
>             Fix For: 0.10.1.0, 0.10.0.1
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The javadocs for the new consumer indicate that auto commit breaks at least once delivery.
This is no longer correct as of 0.10. 
> http://kafka.apache.org/0100/javadoc/index.html?org/apache/kafka/clients/consumer/KafkaConsumer.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message