You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Anonymous (Jira)" <ji...@apache.org> on 2023/04/13 10:59:00 UTC

[jira] [Updated] (BEAM-8456) Add pipeline option to control truncate of BigQuery data processed by Beam SQL

     [ https://issues.apache.org/jira/browse/BEAM-8456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anonymous updated BEAM-8456:
----------------------------
    Status: Triage Needed  (was: Resolved)

> Add pipeline option to control truncate of BigQuery data processed by Beam SQL
> ------------------------------------------------------------------------------
>
>                 Key: BEAM-8456
>                 URL: https://issues.apache.org/jira/browse/BEAM-8456
>             Project: Beam
>          Issue Type: Improvement
>          Components: dsl-sql
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>            Priority: P2
>             Fix For: 2.18.0
>
>          Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> Most of the time, a user reading a timestamp from BigQuery with higher-than-millisecond precision timestamps may not even realize that the data source created these high precision timestamps. They are probably timestamps on log entries generated by a system with higher precision.
> If they are using it with Beam SQL, which only supports millisecond precision, it makes sense to "just work" by default.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)