beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-483) Generated job names easily collide
Date Fri, 22 Jul 2016 23:44:20 GMT


ASF GitHub Bot commented on BEAM-483:

GitHub user peihe opened a pull request:

    [BEAM-483] Moves NormalizedUniqueName to ApplicationNameOptions, and uses it in runners.


You can merge this pull request into a Git repository by running:

    $ git pull job-name

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #719
commit e597582da820016f97709c847329237841a3ddd6
Author: Pei He <>
Date:   2016-07-22T23:40:54Z

    [BEAM-483] Move NormalizedUniqueName to ApplicationNameOptions


> Generated job names easily collide
> ----------------------------------
>                 Key: BEAM-483
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow
>            Reporter: Pei He
>            Assignee: Pei He
>            Priority: Minor
> The current job name generation scheme may easily lead to duplicate job names and cause
DataflowJobAlreadyExistsException, especially when a series of jobs are submitted at the same
time. (e.g., from a single script).
> It would be better to just add a random suffix like "-3275" or "-x1bh".

This message was sent by Atlassian JIRA

View raw message