feat: Enable Lossless Timestamps in BQ java client lib #3589
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.
With discovery revision 20240124 or later, the BQ discovery document now properly exposes the API functionality to use lossless timestamps (DataFormatOptions.UseInt64Timestamp). This can be supplied as part of the jobs.query request, as well as passed as arguments to tabledata.list / jobs.getQueryResults.
This change enables the toggling of lossless timestamps in the java client library for BQ. The former format is still usable and is used by default. Users must opt in to use this feature.