[
https://issues.apache.org/jira/browse/KAFKA-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597433#comment-16597433
]
Matthias J. Sax edited comment on KAFKA-6690 at 8/30/18 1:21 PM:
-----------------------------------------------------------------
[~nafshartous] It's your KIP and thus your decision if you want to follow this
suggesting or not. It would be good to understand the advantages and
disadvantage of your current (simplified?) proposal compared to the suggestion.
What you can do/not do with the or the other? Would it be possible to extend
your current proposal with something more generic later on?
You can also just continue the VOTE if you are not interested to change the
proposal. A single non-binding downvote does not block the KIP. I will also
follow up on the mailing list.
Note, that anybody can do a KIP and she/he is in the "driver seat" to lead the
discussion. Thus, you can agree with any other proposal and change your KIP or
argue against it (why do you think it's not necessary etc.). In the end, if you
can convince the community that your KIP is valuable you will get it through.
Just keep discussion and sharing your point of view on the mailing list, why
you want to do what, and lay out the advantages/disadvantages compare to
alternative proposals.
was (Author: mjsax):
[~nafshartous] It's your KIP and thus your decision if you want to follow this
suggesting or not. It would be good to understand the advantages and
disadvantage of your current (simplified?) proposal compared to the suggestion.
What you can do/not do with the or the other? Would it be possible to extend
your current proposal with something more generic later on?
You can also just continue the VOTE if you are not interested to change the
proposal. A single non-binding downvote does not block the KIP. I will also
follow up on the mailing list.
> 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)
