[ 
https://issues.apache.org/jira/browse/BEAM-7689?focusedWorklogId=274914&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-274914
 ]

ASF GitHub Bot logged work on BEAM-7689:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 10/Jul/19 15:18
            Start Date: 10/Jul/19 15:18
    Worklog Time Spent: 10m 
      Work Description: chamikaramj commented on issue #9013: [BEAM-7689] make 
a temporary directory unique for FileBaseSink
URL: https://github.com/apache/beam/pull/9013#issuecomment-510106297
 
 
   Run Dataflow ValidatesRunner
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 274914)
    Time Spent: 1.5h  (was: 1h 20m)

> 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: Blocker
>             Fix For: 2.7.1, 2.14.0
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Temporary directory for WriteOperation in FileBasedSink is generated from a 
> second-granularity timestamp (yyyy-MM-dd_HH-mm-ss) and unique increasing 
> index. 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)

Reply via email to