> On Jan 16, 2019, at 9:51 PM, [email protected] wrote:
>
> Hi all,
>
> On the dev list we’ve been discussing a proposed new feature (prioritized
> topics). In a nutshell, when consuming from a set of topics with assigned
> priorities, consumption from lower-priority topics only occurs if there’s no
> data flowing in from a higher-priority topic.
>
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-349%3A+Priorities+for+Source+Topics
>
> <https://cwiki.apache.org/confluence/display/KAFKA/KIP-349%3A+Priorities+for+Source+Topics><https://cwiki.apache.org/confluence/display/KAFKA/KIP-349:+Priorities+for+Source+Topics
>
> <https://cwiki.apache.org/confluence/display/KAFKA/KIP-349:+Priorities+for+Source+Topics>>
>
> One question is are there use-cases for the proposed API. If you think this
> would be useful and have use-cases in mind please reply with the use-cases.
>
> Its also possible to implement prioritization with the existing API by using
> a combination of pausing, resuming, and local buffering. The question is
> then does it make sense to introduce the proposed higher-level API to make
> this easier ?
>
> The responses will be used as input to determine if we move ahead with the
> proposal. Thanks in advance for input.
Hi all,
Thanks for everyone’s input. After a very long discussion on the dev list
we’re not moving forward with KIP-349. Some felt that this feature could be
achieved by using existing capabilities of the current consumer API. See the
thread on the dev list (with KIP-349 in subject heading) for more details.
Cheers,
--
Nick
