[
https://issues.apache.org/jira/browse/KAFKA-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548673#comment-13548673
]
Neha Narkhede commented on KAFKA-690:
-------------------------------------
The protocol was meant to do this, so checked it on 0.8 branch.
> TopicMetadataRequest throws exception when no topics are specified
> ------------------------------------------------------------------
>
> Key: KAFKA-690
> URL: https://issues.apache.org/jira/browse/KAFKA-690
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8
> Reporter: David Arthur
> Fix For: 0.8
>
> Attachments: KAFKA-690.patch
>
>
> If no topics are sent in a TopicMetadataRequest, `readFrom` throws an
> exception when trying to get the the head of the topic list for a debug
> statement.
> java.util.NoSuchElementException: head of empty list
> at scala.collection.immutable.Nil$.head(List.scala:386)
> at scala.collection.immutable.Nil$.head(List.scala:383)
> at
> kafka.api.TopicMetadataRequest$$anonfun$readFrom$2.apply(TopicMetadataRequest.scala:43)
> at
> kafka.api.TopicMetadataRequest$$anonfun$readFrom$2.apply(TopicMetadataRequest.scala:43)
> at kafka.utils.Logging$class.debug(Logging.scala:51)
> at kafka.api.TopicMetadataRequest$.debug(TopicMetadataRequest.scala:25)
> at
> kafka.api.TopicMetadataRequest$.readFrom(TopicMetadataRequest.scala:43)
> at kafka.api.RequestKeys$$anonfun$4.apply(RequestKeys.scala:37)
> at kafka.api.RequestKeys$$anonfun$4.apply(RequestKeys.scala:37)
> at kafka.network.RequestChannel$Request.<init>(RequestChannel.scala:47)
> at kafka.network.Processor.read(SocketServer.scala:320)
> at kafka.network.Processor.run(SocketServer.scala:231)
> at java.lang.Thread.run(Thread.java:680)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
