[ 
https://issues.apache.org/jira/browse/BEAM-4417?focusedWorklogId=170049&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-170049
 ]

ASF GitHub Bot logged work on BEAM-4417:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 27/Nov/18 23:23
            Start Date: 27/Nov/18 23:23
    Worklog Time Spent: 10m 
      Work Description: pabloem commented on issue #5755: [BEAM-4417] Support 
BigQuery's NUMERIC type using Java
URL: https://github.com/apache/beam/pull/5755#issuecomment-442257052
 
 
   FWIW I'll note that I've implemented a test that verifies this functionality 
and runs internally at Google.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 170049)
    Time Spent: 7.5h  (was: 7h 20m)

> BigqueryIO Numeric datatype Support
> -----------------------------------
>
>                 Key: BEAM-4417
>                 URL: https://issues.apache.org/jira/browse/BEAM-4417
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-gcp
>    Affects Versions: 2.4.0
>            Reporter: Kishan Kumar
>            Assignee: Pablo Estrada
>            Priority: Critical
>              Labels: newbie, patch
>             Fix For: 2.7.0
>
>          Time Spent: 7.5h
>  Remaining Estimate: 0h
>
> The BigQueryIO.read fails while parsing the data from the avro file generated 
> while reading the data from the table which has columns with *Numeric* 
> datatypes. 
> We have gone through the source code at Git-Hub and noticed that *Numeric 
> data type is not yet supported.* 
>  
> Caused by: com.google.common.base.VerifyException: Unsupported BigQuery type: 
> NUMERIC
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to