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

Dariusz Aniszewski commented on BEAM-3406:
------------------------------------------

Thanks [~alanmyrvold] for creating table, I naively assumed it will be 
automatically created.

[~chamikara] After some thinking I plan to modify seed job for those tests. 
Currently there is just one job that executes all the tests one by one and 
uploads results to the same BigQuery table. It was easiest thing to do in the 
first place but it doesn't have much sense in the long run. I'm planning to 
change the seed job to create a separate Jenkins job for each case, so it will 
be possible to track results and compare them over time. [~alanmyrvold] would 
you be able to create few more tables this week?

I can also take a look the perfkit issue you pointed as well as the one that 
[~ŁukaszG] filed few days ago that seems related: 
https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/issues/1552

> FIeBasedIO IT fails due to "BigQuery error"
> -------------------------------------------
>
>                 Key: BEAM-3406
>                 URL: https://issues.apache.org/jira/browse/BEAM-3406
>             Project: Beam
>          Issue Type: Bug
>          Components: testing
>            Reporter: Chamikara Jayalath
>            Assignee: Łukasz Gajowy
>         Attachments: schema, textioit
>
>
> For example, 
> https://builds.apache.org/view/A-D/view/Beam/job/beam_PerformanceTests_FileBasedIO_IT/54/console
> beam_performance.filebasedioit_pkb_results 
> /tmp/perfkitbenchmarker/runs/e2e3d02d/perfkit-bq-pub3ntgN3.json. Got return 
> code (1).
> STDOUT: BigQuery error in load operation: No schema specified on job or table.
> STDERR: 
> /usr/lib/google-cloud-sdk/platform/bq/third_party/oauth2client/contrib/gce.py:73:
>  UserWarning: You have requested explicit scopes to be used with a GCE 
> service account.
> Using this argument will have no effect on the actual scopes for tokens
> requested. These scopes are set at VM instance creation time and
> can't be overridden in the request.
>   warnings.warn(_SCOPES_WARNING)
> Lukasz and Darek, can you take a look ?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to