[
https://issues.apache.org/jira/browse/KAFKA-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659806#comment-16659806
]
Bala Prassanna I commented on KAFKA-6690:
-----------------------------------------
[~nafshartous] Sorry about the delay in reply. We use Kafka to process the
aynchronous events of our Document Management System such as preview
generation, indexing for search etc. The traffic gets generated via Web and
Desktop Sync application. In such cases, we had to prioritise the traffic from
web and consume them first. Though this may lead to starvation of events from
sync, an API as such will help us effectively manage the available resources
and prioritise our traffic without allocating separate server to handle the
sync load.
> Priorities for Source Topics
> ----------------------------
>
> Key: KAFKA-6690
> URL: https://issues.apache.org/jira/browse/KAFKA-6690
> Project: Kafka
> Issue Type: New Feature
> Components: consumer
> 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)
