[SPARK-56243][SS] Throw detailed error on malformed Kafka record timestamps#55038
Closed
kavpreetgrewal wants to merge 2 commits intoapache:masterfrom
Closed
[SPARK-56243][SS] Throw detailed error on malformed Kafka record timestamps#55038kavpreetgrewal wants to merge 2 commits intoapache:masterfrom
kavpreetgrewal wants to merge 2 commits intoapache:masterfrom
Conversation
Contributor
|
Looks OK to me. Would it be able to come up with test? I guess this should be very easy to reproduce from the description? |
Contributor
|
https://github.com/kavpreetgrewal/spark/actions/runs/23923726141/job/69775901628 I've confirmed the CI failure is not relevant. |
Contributor
|
Thanks! Merging to master. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Throw a detailed
KAFKA_MALFORMED_RECORD_TIMESTAMPmessage when a record has a malformed or incorrect precision timestamp.Why are the changes needed?
Some users may use custom producers which set the timestamp to an incorrect precision level than what is expected by Kafka. Upon hitting this issue, they would get a generic arithmetic overflow error.
Does this PR introduce any user-facing change?
Yes, it introduces a new error message, however there is no other behavioral change.
How was this patch tested?
N/A
Was this patch authored or co-authored using generative AI tooling?
No.