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

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

                Author: ASF GitHub Bot
            Created on: 26/Jun/18 19:35
            Start Date: 26/Jun/18 19:35
    Worklog Time Spent: 10m 
      Work Description: kennknowles commented on issue #5755: [BEAM-4417] 
Support BigQuery's NUMERIC type using Java
URL: https://github.com/apache/beam/pull/5755#issuecomment-400436045
 
 
   This LGTM as far as it goes. Should I hope for a test that does some 
end-to-end thing and get the numeric out?

----------------------------------------------------------------
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: 116113)
    Time Spent: 20m  (was: 10m)

> 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: Chamikara Jayalath
>            Priority: Critical
>              Labels: newbie, patch
>             Fix For: 2.6.0
>
>          Time Spent: 20m
>  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