You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Nick Afshartous (JIRA)" <ji...@apache.org> on 2018/06/29 19:17:00 UTC
[jira] [Commented] (KAFKA-6690) Priorities for Source Topics
[ https://issues.apache.org/jira/browse/KAFKA-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16528109#comment-16528109 ]
Nick Afshartous commented on KAFKA-6690:
----------------------------------------
This seems like it would require an API change. For example, if we added a new class
{code}
TopicPrioritiy(java.lang.String topic, int priority)
{code}
then there would be a new {{KafkaConsumer.subscribe}} method
{code}
public void subscribe(java.util.List<TopicPriority> topicPriorities)
{code}
Doe this capture then intent ?
> Priorities for Source Topics
> ----------------------------
>
> Key: KAFKA-6690
> URL: https://issues.apache.org/jira/browse/KAFKA-6690
> Project: Kafka
> Issue Type: New Feature
> Components: streams
> Reporter: Bala Prassanna I
> Priority: Major
>
> We often encounter use cases where we need to prioritise source topics. If a consumer is listening more than one topic, say, HighPriorityTopic and LowPriorityTopic, it should consume events from LowPriorityTopic only when all the events from HighPriorityTopic are consumed. This is needed in Kafka Streams processor topologies as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)