[
https://issues.apache.org/jira/browse/BEAM-14529?focusedWorklogId=775589&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-775589
]
ASF GitHub Bot logged work on BEAM-14529:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 27/May/22 22:53
Start Date: 27/May/22 22:53
Worklog Time Spent: 10m
Work Description: yirutang commented on PR #17779:
URL: https://github.com/apache/beam/pull/17779#issuecomment-1140089460
@chamikaramj @reuvenlax
Issue Time Tracking
-------------------
Worklog Id: (was: 775589)
Time Spent: 50m (was: 40m)
> Beam BQIO not accepting integer values for BQ table fields of type Float64
> --------------------------------------------------------------------------
>
> Key: BEAM-14529
> URL: https://issues.apache.org/jira/browse/BEAM-14529
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
> Reporter: Yiru Tang
> Assignee: Yiru Tang
> Priority: P2
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Customer (F5) is working on migrating to the new Storage API support in Beam
> SDK and are facing issues in the latest Snapshot build. Today, in production,
> they are using the legacy streaming API and their pipeline works fine when
> they are mapping an incoming integer field to a BQ table field of type
> Float64. However, with the storage API, their pipeline is failing with the
> following error "Unexpected value :0, type: class java.lang.Integer. Table
> field name: a, type: FLOAT64" Customer considers this as a regression and is
> preventing them from going live with Storage API. Customer is planning on
> going live with Storage API end of July and would like to have this fixed in
> the 2.39.0 GA release.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
