You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Filipe Regadas (JIRA)" <ji...@apache.org> on 2019/07/26 15:49:00 UTC
[jira] [Updated] (BEAM-7830) SparkPipelineResult waitUntilFinish
duration not consistent with DataflowJob
[ https://issues.apache.org/jira/browse/BEAM-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Filipe Regadas updated BEAM-7830:
---------------------------------
Description:
`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`
was:
`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`
> SparkPipelineResult waitUntilFinish duration not consistent with DataflowJob
> ----------------------------------------------------------------------------
>
> 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
> Priority: Minor
>
> `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)