feat: Row readers using storage API acceleration can leverage full precision avro values#7525
Merged
gcf-merge-on-green[bot] merged 2 commits intomainfrom Mar 5, 2026
Merged
Conversation
danieljbruce
added
the
automerge
alvarowolfx
approved these changes
Mar 5, 2026
gcf-merge-on-green
bot
removed
the
automerge
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
2 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.
Description
Copied from googleapis/nodejs-bigquery-storage#658
This PR allows users to fetch high precision timestamps for read calls with avro readers. Previous to this PR there was no way users could fetch such timestamps.
Impact
With a custom Avro reader, now users can fetch and consume data from the server that preserves high precision timestamps on the backend while providing information about the avro reader in the request.
Testing
A system test is added that proves the timestamp fetched from the server is high precision.
Additional Information
The source code changes are pretty much exactly in the same place as those from googleapis/nodejs-bigquery-storage#656. The main difference is data coming back from the server for arrow readers is very different from data coming back from avro readers. That means instead of using arrow reader transforms from the source code we need to leverage the avsc library to parse server results in the same way that the quickstart guide demonstrates. This allows the test to produce a high precision timestamp.