You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/10 17:07:25 UTC

[jira] [Commented] (BEAM-8289) Failing the job when the temporary file is accidentally deleted by another job in FileBasedSink

    [ https://issues.apache.org/jira/browse/BEAM-8289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174640#comment-17174640 ] 

Beam JIRA Bot commented on BEAM-8289:
-------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> Failing the job when the temporary file is accidentally deleted by another job in FileBasedSink
> -----------------------------------------------------------------------------------------------
>
>                 Key: BEAM-8289
>                 URL: https://issues.apache.org/jira/browse/BEAM-8289
>             Project: Beam
>          Issue Type: Bug
>          Components: io-java-files
>            Reporter: Heejong Lee
>            Priority: P2
>              Labels: stale-P2
>
> There was an issue that a temporary directory name is not unique in FileBasedSink (https://issues.apache.org/jira/browse/BEAM-7689) and we've changed the naming algorithm from timestamp to UUID. However, it looks like UUID is still not enough to distinguish two separate temporary directories from different jobs. We may need to fail the job when the temporary file is accidentally deleted by another job.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)