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

Posted to commits@beam.apache.org by "Kamil Szewczyk (JIRA)" <ji...@apache.org> on 2018/04/24 09:15:00 UTC

[jira] [Commented] (BEAM-4153) Performance tests for spark runner fail

    [ https://issues.apache.org/jira/browse/BEAM-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449511#comment-16449511 ] 

Kamil Szewczyk commented on BEAM-4153:
--------------------------------------

I was recently playing a lot with BigQuerry when working on anomaly detection tool and noticed that in db schema timestamp is defined as FLOAT. Perfkit also produces it as a float 'timestamp': 1524485484.41655, so the upload passes. Probably it was defined as float from the beginning because of how perfkit produces it. 

> Performance tests for spark runner fail
> ---------------------------------------
>
>                 Key: BEAM-4153
>                 URL: https://issues.apache.org/jira/browse/BEAM-4153
>             Project: Beam
>          Issue Type: Bug
>          Components: testing
>            Reporter: Etienne Chauchot
>            Assignee: Jason Kuster
>            Priority: Major
>
> The error seems to be that one:
> BigQuery error in load operation: Error processing job
> 'apache-beam-testing:bqjob_r2527a0e444514f2b_00000162f128db2b_1': Invalid schema
> update. Field timestamp has changed type from TIMESTAMP to FLOAT



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