[
https://issues.apache.org/jira/browse/FLINK-7265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16104686#comment-16104686
]
ASF GitHub Bot commented on FLINK-7265:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/4397
How about I just remove the consistency level completely and reduce the
`FileSystemKind` to "file system" and "object store"?
I tried to think through the ecosystem of file systems quite a bit and this
stuck me as a good compromise, but there are of course at least 10 other ways
to do that. Seems that this discussion is mainly about "why like this and not
possibly like that" and there are of course pros and cons for each approach,
depending on your view of that ecosystem. We can guess how to do that now or
try to evolve later as we discover more requirements and more file system types.
In any case, my main concern here is to fix the FileStateHandle release for
1.3.2, so let's strip this down to the bare minimum and get this done?
> FileSystems should describe their kind and consistency level
> ------------------------------------------------------------
>
> Key: FLINK-7265
> URL: https://issues.apache.org/jira/browse/FLINK-7265
> Project: Flink
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.3.1
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Fix For: 1.4.0, 1.3.2
>
>
> Currently, all {{FileSystem}} types look the same to Flink.
> However, certain operations should only be executed on certain kinds of file
> systems.
> For example, it makes no sense to attempt to delete an empty parent directory
> on S3, because there are no such thinks as directories, only hierarchical
> naming in the keys (file names).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
