You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/10/09 15:37:00 UTC

[jira] [Commented] (KAFKA-8954) Topic existence check is wrongly implemented in the DeleteOffset API

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

ASF GitHub Bot commented on KAFKA-8954:
---------------------------------------

hachikuji commented on pull request #7406: KAFKA-8954; Topic existence check is wrongly implemented in the DeleteOffset API (KIP-496)
URL: https://github.com/apache/kafka/pull/7406
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Topic existence check is wrongly implemented in the DeleteOffset API
> --------------------------------------------------------------------
>
>                 Key: KAFKA-8954
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8954
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: David Jacot
>            Assignee: David Jacot
>            Priority: Major
>
> The current DeleteOffset API check relies on the consumer group's committed offsets to decide if a topic exists or not. While this works in most of the cases, it does not work when a topic exists but it does not have any committed offsets yet. Moreover, it is not consistent with other APIs which rely on the metadata cache so it must be updated.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)