[
https://issues.apache.org/jira/browse/KAFKA-12638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317635#comment-17317635
]
A. Sophie Blee-Goldman commented on KAFKA-12638:
------------------------------------------------
Nope, no such things as credits in Kafka -- technically anyone can pick up
anything, and the major deciding factor is just your own confidence and
familiarity with Kafka. If you're relatively new to Kafka and pick up something
large that you need a lot of help with, you might struggle to get it done just
because everyone who works on this is always busy (not because they don't want
to help -- they do). We try to label things with newbie and/or newbie++ to
indicate good entry-level tickets.
That said, it never hurts to ask before picking something up -- often if it's a
blocker ticket, or maybe critical, then it's likely that the person who
reported it or someone they know already plan to work on it. But you can always
ask -- and "Major" is the default priority which many tickets are just left at,
so don't let that stop you.
> Remove default implementation of ConsumerRebalanceListener#onPartitionsLost
> ---------------------------------------------------------------------------
>
> Key: KAFKA-12638
> URL: https://issues.apache.org/jira/browse/KAFKA-12638
> Project: Kafka
> Issue Type: Improvement
> Components: consumer
> Reporter: A. Sophie Blee-Goldman
> Priority: Major
>
> When we added the #onPartitionsLost callback to the ConsumerRebalanceListener
> in KIP-429, we gave it a default implementation that just invoked the
> existing #onPartitionsRevoked method for backwards compatibility. This is
> somewhat inconvenient, since we generally want to invoke #onPartitionsLost in
> order to skip the committing of offsets on revoked partitions, which is
> exactly what #onPartitionsRevoked does.
> I don't think we can just remove it in 3.0 since we haven't indicated that we
> "deprecated" the default implementation or logged a warning that we intend to
> remove the default in a future release (as we did for the
> RocksDBConfigSetter#close method in Streams, for example). We should try to
> add such a warning now, so we can remove it in a future release.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
