[
https://issues.apache.org/jira/browse/BEAM-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993906#comment-15993906
]
Mark Liu edited comment on BEAM-1986 at 5/2/17 10:28 PM:
---------------------------------------------------------
What is "name of the main application" exactly mean? In my opinion, for testing
it probably can be like "TestClassName-TestFunctionName". For general pipeline,
it can be "Class/ModuleName".
I found
[inspect|https://docs.python.org/2.7/library/inspect.html#inspect.getframeinfo]
may be useful, which can get caller stacktrace. However, someone mentioned
[here|http://stackoverflow.com/a/2654130] that it's not recommended for
production code since it depends on CPython environment.
was (Author: markflyhigh):
What is "name of the main application" exactly mean? Ideally for testing, it
probably can be like "TestClassName-TestFunctionName". For general pipeline, it
can be "Class/ModuleName".
I found
[inspect|https://docs.python.org/2.7/library/inspect.html#inspect.getframeinfo]
may be useful, which can get caller stacktrace. However, someone mentioned
[here|http://stackoverflow.com/a/2654130] that it's not recommended for
production code since it depends on CPython environment.
> Job ALREADY_EXISTS in post commit
> ---------------------------------
>
> Key: BEAM-1986
> URL: https://issues.apache.org/jira/browse/BEAM-1986
> Project: Beam
> Issue Type: Bug
> Components: sdk-py
> Reporter: Ahmet Altay
> Assignee: Mark Liu
> Priority: Minor
>
> I noticed a job failed with ALREDY_EXISTS error, a sign of same {{job_name}}
> auto generated twice. Could we add a 1 second delay to prevent things like
> this?
> https://builds.apache.org/view/Beam/job/beam_PostCommit_Python_Verify/1877/consoleFull
> cc: [~pabloem] Another perspective, would it make sense to add a small random
> component (e.g. 1-2 digits) to job name to reduce this issue? Or perhaps
> include ms resolution.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
