Skip to content

produce: set MaxTimestamp #3108

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 28, 2025
Merged

produce: set MaxTimestamp #3108

merged 1 commit into from
Feb 28, 2025

Conversation

rockwotj
Copy link
Contributor

Similar to other clients, set the MaxTimestamp computed from the records
in the batch.

Similar to other clients, set the MaxTimestamp computed from the records
in the batch.

Signed-off-by: Tyler Rockwood <[email protected]>
@lienmeat
Copy link

This issue is blocking us from using sarama with redpanda, which currently depends on MaxTimestamp being set, otherwise offset for time functionality does not work correctly on partitions with message.timestamp.type = CreateTime if produced via sarama.

Copy link
Contributor

@puellanivis puellanivis left a comment

Choose a reason for hiding this comment

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

I see nothing to comment on.

@rockwotj rockwotj requested a review from puellanivis February 28, 2025 05:20
Copy link
Collaborator

@dnwe dnwe left a comment

Choose a reason for hiding this comment

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

Thanks for the contribution!

@dnwe dnwe merged commit 3c67885 into IBM:main Feb 28, 2025
16 checks passed
@dnwe dnwe added the fix label Mar 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants