[
https://issues.apache.org/jira/browse/BEAM-4153?focusedWorklogId=94958&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-94958
]
ASF GitHub Bot logged work on BEAM-4153:
----------------------------------------
Author: ASF GitHub Bot
Created on: 25/Apr/18 07:17
Start Date: 25/Apr/18 07:17
Worklog Time Spent: 10m
Work Description: echauchot commented on a change in pull request #5206:
[BEAM-4153] Fixing performance test of spark, added option to trigger…
URL: https://github.com/apache/beam/pull/5206#discussion_r183959844
##########
File path: .test-infra/jenkins/job_beam_PerformanceTests_Spark.groovy
##########
@@ -37,7 +41,8 @@ job('beam_PerformanceTests_Spark'){
// There are currently problems uploading to Dataproc, so we use a file
// already present on the machines as input.
dpb_wordcount_input: '/etc/hosts',
- config_override:
'dpb_wordcount_benchmark.dpb_service.service_type=dataproc'
+ config_override:
'dpb_wordcount_benchmark.dpb_service.service_type=dataproc',
+ bigquery_table: 'beam_performance.spark_pkp_results'
Review comment:
I guess you dedicated a new table to spark output. As the test passes, seems
good to me
----------------------------------------------------------------
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: 94958)
Time Spent: 1h 10m (was: 1h)
> 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
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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)
