[SPARK-55107] Log TID for scanned file in FileScanRDD #53876
+3
−2
Conversation
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
JIRA Issue Information=== Improvement SPARK-55107 === This comment was automatically generated by GitHub Actions |
turboFei
force-pushed
the
filescan_tid
branch
from
592bb61 to
3d9822c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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?
Log TID for scanned file in FileScanRDD.
Why are the changes needed?
Similar with #46966.
User story:
When we encounter Parquet file corruption in production, we typically have the Task ID (TID) from the error message. However, executor logs contain interleaved log messages from multiple tasks running concurrently. Without TID in the file scan logs, we cannot easily determine which specific files were scanned by the failing task, making it difficult to narrow down which Parquet file is corrupted.
By logging the TID alongside the scanned file path, we can now filter executor logs by the failing task's TID and quickly identify the exact set of files that were processed by that task.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Review, as it only touches log contents.
Was this patch authored or co-authored using generative AI tooling?
No.