feat: Add picosecond timestamp support#1590
feat: Add picosecond timestamp support#1590google-labs-jules[bot] wants to merge 1 commit intomainfrom
Conversation
Added `timestampPrecision` to `ITableFieldSchema` in types. Updated `convertSchemaFieldValue` to return raw string for TIMESTAMP fields with `timestampPrecision: '12'` to preserve picosecond precision, bypassing `PreciseDate` truncation.
|
👋 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. |
This change adds support for picosecond precision timestamps, aligning with recent changes in the BigQuery Java client.
src/types.d.tsto includetimestampPrecisioninITableFieldSchema.src/bigquery.tsto check fortimestampPrecision === '12'inconvertSchemaFieldValue. If detected, the value is returned as a string rather than being converted to aPreciseDateobject (which only supports nanosecond precision), ensuring no data loss for picosecond values.PR created automatically by Jules for task 7439807773758684812 started by @danieljbruce