Skip to content

fix(ISV-6436): update metadata to support older Python versions#8

Merged
BorekZnovustvoritel merged 3 commits intomainfrom
ISV-6436
Feb 16, 2026
Merged

fix(ISV-6436): update metadata to support older Python versions#8
BorekZnovustvoritel merged 3 commits intomainfrom
ISV-6436

Conversation

@BorekZnovustvoritel
Copy link
Contributor

@BorekZnovustvoritel BorekZnovustvoritel commented Feb 11, 2026

This PR is meant to be reviewed per commit. But all these changes are related as the problems started manifesting with the bump of confluent_kafka.

@BorekZnovustvoritel BorekZnovustvoritel force-pushed the ISV-6436 branch 2 times, most recently from 227b486 to 45e2217 Compare February 11, 2026 13:03
Signed-off-by: Marek Szymutko <mszymutk@redhat.com>
Signed-off-by: Marek Szymutko <mszymutk@redhat.com>
Signed-off-by: Marek Szymutko <mszymutk@redhat.com>
TopicPartition(
topic=partition_info.topic,
partition=partition_info.partition,
offset=max_to_commit + 1,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These changes look weird, let me explain:

  • Kafka needs message commits to be +1 than the latest confirmed messages
  • In the past, the tracker class had the exact values of offsets from messages
  • Now that I added the commit retry, there is a chance we may need to return commits back to the tracker class. I think it's cleaner to add the +1 when the offset is first stored in the tracker object, because otherwise the retry (re-register) of commits needs to again subtract the -1.

This changes the behavior of the tracker class slightly, but it was never meant to be used directly, it's just called from the BaseConsumer where it's a private attribute.

Copy link

@mantomas mantomas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@BorekZnovustvoritel BorekZnovustvoritel merged commit d80bee1 into main Feb 16, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants