[ https://issues.apache.org/jira/browse/BEAM-4283?focusedWorklogId=109735&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-109735 ]
ASF GitHub Bot logged work on BEAM-4283: ---------------------------------------- Author: ASF GitHub Bot Created on: 07/Jun/18 15:16 Start Date: 07/Jun/18 15:16 Worklog Time Spent: 10m Work Description: echauchot commented on issue #5464: [BEAM-4283] Write Nexmark execution times to bigquery URL: https://github.com/apache/beam/pull/5464#issuecomment-395458493 @chamikaramj I missed part of the stacktrace. I know where the serialization issue come from: I use PipelineOptions in a SerializableFunction used to configure the IO. ---------------------------------------------------------------- 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: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 109735) Time Spent: 6h 40m (was: 6.5h) > Export nexmark execution times to bigQuery > ------------------------------------------ > > Key: BEAM-4283 > URL: https://issues.apache.org/jira/browse/BEAM-4283 > Project: Beam > Issue Type: Sub-task > Components: examples-nexmark > Reporter: Etienne Chauchot > Assignee: Etienne Chauchot > Priority: Major > Time Spent: 6h 40m > Remaining Estimate: 0h > > Nexmark only outputs the results collection to bigQuery and prints in the > console the execution times. To supervise Nexmark execution times, we need to > store them as well per runner/query/mode -- This message was sent by Atlassian JIRA (v7.6.3#76005)