[
https://issues.apache.org/jira/browse/BEAM-7830?focusedWorklogId=284205&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-284205
]
ASF GitHub Bot logged work on BEAM-7830:
----------------------------------------
Author: ASF GitHub Bot
Created on: 29/Jul/19 12:16
Start Date: 29/Jul/19 12:16
Worklog Time Spent: 10m
Work Description: iemejia commented on issue #9170: [BEAM-7830]: make
spark default duration consistent with PipelineResult
URL: https://github.com/apache/beam/pull/9170#issuecomment-515966662
Run Spark ValidatesRunner
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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: 284205)
Time Spent: 20m (was: 10m)
> SparkPipelineResult waitUntilFinish duration not consistent with
> PipelineResult
> -------------------------------------------------------------------------------
>
> Key: BEAM-7830
> URL: https://issues.apache.org/jira/browse/BEAM-7830
> Project: Beam
> Issue Type: Bug
> Components: runner-spark
> Affects Versions: 2.13.0
> Reporter: Filipe Regadas
> Assignee: Filipe Regadas
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> `DataflowPipelineJob` default duration on `waitUntilFinish` is
> `Duration.millis(-1)` which is inline with `PipelineResult#waitUntilFinish`
> doc <= 1ms results in infinite wait.
> However, `SparkPipelineResult#waitUntilFinish` uses
> `Duration.millis(Long.MAX_VALUE)` hence not being consistent with
> `PipelineResult#waitUntilFinish`
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
