[
https://issues.apache.org/jira/browse/KAFKA-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16560402#comment-16560402
]
Guozhang Wang commented on KAFKA-6690:
--------------------------------------
If we add it on the consumer API, then Streams may be automatically geared with
this feature since it is leveraging on consumers (some different considerata
would be done on Streams since today its messaging choosing is purely dependent
on timestamp synchronization, but this can be deferred to a follow-up
discussion).
Maybe you can start the discussion thread on the mailing list and ask for the
community's opinion on this feature request.
> 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
> Assignee: Nick Afshartous
> 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)
