You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2013/11/09 05:09:18 UTC
[jira] [Commented] (SAMZA-83) Discard rather than throw exception
for Kafka topics with non-existent partitions
[ https://issues.apache.org/jira/browse/SAMZA-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817999#comment-13817999 ]
Chris Riccomini commented on SAMZA-83:
--------------------------------------
+1
This should be reverted when SAMZA-82 is resolved.
> Discard rather than throw exception for Kafka topics with non-existent partitions
> ---------------------------------------------------------------------------------
>
> Key: SAMZA-83
> URL: https://issues.apache.org/jira/browse/SAMZA-83
> Project: Samza
> Issue Type: Bug
> Components: kafka
> Affects Versions: 0.7.0
> Reporter: Jakob Homan
> Assignee: Jakob Homan
> Fix For: 0.7.0
>
> Attachments: SAMZA-83.patch
>
>
> KafkaSystemConsumer, 117:
> {code} val brokerOption = partitionMetadata(topicAndPartition.topic)
> .partitionsMetadata
> .find(_.partitionId == topicAndPartition.partition)
> .getOrElse(toss("Can't find leader for %s" format topicAndPartition))
> .leader{code}
> In conjunction with SAMZA-82, we can't ready kafka streams with different number of partitions, since we throw exceptions for those topics that we speculatively created. This is short term fix; the more correct approach is SAMZA-82.
--
This message was sent by Atlassian JIRA
(v6.1#6144)