You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/12 03:51:03 UTC
[jira] [Updated] (BEAM-4747) Python LocalFileSystem directory-creation semantics
[ https://issues.apache.org/jira/browse/BEAM-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenneth Knowles updated BEAM-4747:
----------------------------------
This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.
> Python LocalFileSystem directory-creation semantics
> ---------------------------------------------------
>
> Key: BEAM-4747
> URL: https://issues.apache.org/jira/browse/BEAM-4747
> Project: Beam
> Issue Type: Improvement
> Components: sdk-py-core
> Affects Versions: 2.5.0
> Reporter: Ryan Williams
> Priority: P3
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> Coming out of discussion on [BEAM-4742|https://issues.apache.org/jira/browse/BEAM-4742] / [#5903|https://github.com/apache/beam/pull/5903] is a question of whether {{LocalFileSystem.{open,create,copy,rename}}} should create intermediate (destination) directories, or fail with {{IOError}}'s (as the stdlib {{os}} module generally will).
> If the semantics of {{LocalFileSystem}} should mimic those of distributed filesystems (in the spirit of [recent discussion about {{DirectRunner}} being more like a local simulation of a distributed runner than a production-grade local runner|https://www.mail-archive.com/dev@beam.apache.org/msg08410.html]), then this makes sense, and it sounds like [~lcwik] and [~angoenka] are in favor of this interpretation.
> I'll repurpose [#5903|https://github.com/apache/beam/pull/5903] to this end unless I hear otherwise.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)