[
https://issues.apache.org/jira/browse/KAFKA-15551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827989#comment-17827989
]
Lianet Magrans commented on KAFKA-15551:
----------------------------------------
Hey [~zxcoccer], thanks for jumping in! This one should definitely be a simple
one, as I know that we do handle it already for some API calls (ex. validate
positions early return if no positions to validate
[here|https://github.com/apache/kafka/blob/5c929874b88b3b96f650de0f733d93d42ac535a4/clients/src/main/java/org/apache/kafka/clients/consumer/internals/OffsetsRequestManager.java#L227]).
Still, we wanted to verify that we are doing similarly for all the API calls,
to ensure that we're not doing unneeded processing/requests.
We want to have this for 3.8, so the deadline is really tight, but if you have
availability it would be a great help, feel free to re-assign it to you and
ping me anytime if you have questions. Thanks!
> Evaluate conditions for short circuiting consumer API calls
> -----------------------------------------------------------
>
> Key: KAFKA-15551
> URL: https://issues.apache.org/jira/browse/KAFKA-15551
> Project: Kafka
> Issue Type: Improvement
> Components: clients, consumer
> Reporter: Philip Nee
> Assignee: Lianet Magrans
> Priority: Major
> Labels: consumer-threading-refactor, events
> Fix For: 3.8.0
>
>
> For conditions like:
> * Committing empty offset
> * Fetching offsets for empty partitions
> * Getting empty topic partition position
> Should be short circuit possibly at the API level.
> As a bonus, we should double-check whether the existing {{KafkaConsumer}}
> implementation suffers from this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
