Add picosecond timestamp support for Storage Write API#645
Add picosecond timestamp support for Storage Write API#645danieljbruce wants to merge 1 commit intomainfrom
Conversation
Implement Dynamic Protobuf Remapping to support picosecond precision (12 digits) for TIMESTAMP fields. TIMESTAMP fields with timestampPrecision: 12 are now mapped to TYPE_STRING in the generated protobuf descriptors to prevent integer overflow and maintain data fidelity. - Updated protos/google/cloud/bigquery/storage/v1/table.proto to include timestamp_precision. - Updated src/adapt/schema.ts to support timestampPrecision in ITableFieldSchema. - Updated src/adapt/proto.ts to map picosecond TIMESTAMPs to TYPE_STRING. - Added comprehensive unit tests in test/picosecond_timestamp.ts. Co-authored-by: danieljbruce <8935272+danieljbruce@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
product-auto-label
bot
added
size: m
1 participant
This change enables picosecond precision timestamps in the BigQuery Storage Write API by remapping TIMESTAMP fields with precision 12 to strings in the dynamic proto generation phase. This avoids the 64-bit integer limitation of JavaScript for extremely high precision temporal data.
PR created automatically by Jules for task 5248619843397095619 started by @danieljbruce