You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2013/06/13 05:45:19 UTC
[jira] [Resolved] (KAFKA-940) Scala match error in
javaapi.Implicits
[ https://issues.apache.org/jira/browse/KAFKA-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jun Rao resolved KAFKA-940.
---------------------------
Resolution: Fixed
Assignee: Joel Koshy
Thanks for the patch. +1. Committed to 0.8.
> Scala match error in javaapi.Implicits
> --------------------------------------
>
> Key: KAFKA-940
> URL: https://issues.apache.org/jira/browse/KAFKA-940
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8
> Reporter: Joel Koshy
> Assignee: Joel Koshy
> Fix For: 0.8
>
> Attachments: KAFKA-940-v1.patch
>
>
> This would affect javaapi users who (correctly) test for null on API calls (e.g., if (partitionMetadata.leader == null))
> Right now, we actually get a match error:
> scala.MatchError: null
> at kafka.javaapi.Implicits$.optionToJavaRef(Implicits.scala:38)
> at kafka.javaapi.Implicits$.optionToJavaRef(Implicits.scala:40)
> at kafka.javaapi.PartitionMetadata.leader(TopicMetadata.scala:51)
> <truncated>
--
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