[
https://issues.apache.org/jira/browse/BEAM-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16880586#comment-16880586
]
Heejong Lee commented on BEAM-7689:
-----------------------------------
[~tvalentyn] Not a new behavior. It was there at least for the last two years.
This race condition type of bug is very hard to be noticed. I think that's why
this bug wasn't found for such a long time.
> Temporary directory for WriteOperation may not be unique in FileBaseSink
> ------------------------------------------------------------------------
>
> Key: BEAM-7689
> URL: https://issues.apache.org/jira/browse/BEAM-7689
> Project: Beam
> Issue Type: Bug
> Components: io-java-files
> Reporter: Heejong Lee
> Assignee: Heejong Lee
> Priority: Critical
>
> Temporary directory for WriteOperation in FileBasedSink is generated from a
> second-granularity timestamp (yyyy-MM-dd_HH-mm-ss) and unique id. Such
> granularity is not enough to make temporary directories unique between
> different jobs. When two jobs share the same temporary directory, output file
> may not be produced in one job since the required temporary file can be
> deleted from another job.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
