Repository navigation
[chord] add log for arrow flight read - #354
Merged
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds additional logging around Arrow Flight SQL reads in the Spark Doris connector to help observe query submission timing and per-batch/partition read progress.
Changes:
- Log per-batch load metrics (rows + elapsed time) when reading Arrow batches.
- Track and log per-partition totals (batch count and total rows) when closing the reader.
- Log query submission latency for Flight SQL execution.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
catpineapple
approved these changes
Apr 7, 2026
30 of 65 tasks
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
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.
Proposed changes
Issue Number: close #xxx
Problem Summary:
Describe the overview of changes.
Checklist(Required)
Further comments
If this is a relatively large or complex change, kick off the discussion at [email protected] by explaining why you chose the solution you did and what alternatives you considered, etc...