[
https://issues.apache.org/jira/browse/KAFKA-5434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16050915#comment-16050915
]
Vahid Hashemian commented on KAFKA-5434:
----------------------------------------
[~ppatierno] I look at this from a different angle. In the scenario you
described the consumer is just waiting to receive messages in the specified
partition. The partition may not exist yet, but it's always possible to expand
the topic and add more partitions. At that point if a producer sends messages
to that (now existing) partition the consumer would see them. So, in my opinion
this is not a bug, because the consumer is just waiting (vs. hanging).
I understand this is debatable and perhaps others can weigh in.
> Console consumer hangs if not existing partition is specified
> -------------------------------------------------------------
>
> Key: KAFKA-5434
> URL: https://issues.apache.org/jira/browse/KAFKA-5434
> Project: Kafka
> Issue Type: Bug
> Components: tools
> Reporter: Paolo Patierno
> Assignee: Paolo Patierno
>
> Hi,
> if I specify the --partition option for the console consumer with a not
> existing partition for a topic, the application hangs indefinitely.
> Debugging the code I see that it asks for metadata but when it receives topic
> information and it doesn't find the requested partition inside such metadata,
> the code retries new time.
> Could be it worst to check if the partition exists using the partitionFor
> method before calling the assign in the seek of the BaseConsumer and throwing
> an exception so printing an error on the console ?
> Thanks,
> Paolo
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
