[
https://issues.apache.org/jira/browse/BEAM-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757715#comment-16757715
]
Ismaël Mejía commented on BEAM-4822:
------------------------------------
Well when I talk about the Map version is only for the optional metadata of
each filesystem which will probably never coincide, so I am not sure if this
will be covered by a `versionable` type without making most types avoidable
which is almost like the Map idea. Of course this is trying to solve the
problem for all cases, we can be more conservative and just do it for each new
requiement, e.g. for this one only the version, but still I am not even sure
that the version type will align between filesystems which is different from
the principal metadata values (e.g. like lastModifiedDate) and this does not
solve the Coder evolution issue.
> Beam FileIO should support versioned file systems
> -------------------------------------------------
>
> Key: BEAM-4822
> URL: https://issues.apache.org/jira/browse/BEAM-4822
> Project: Beam
> Issue Type: New Feature
> Components: io-java-files
> Reporter: Reuven Lax
> Assignee: Chamikara Jayalath
> Priority: Major
>
> Some file systems (e.g. GCS) are versioned, and support reading previous
> generations of files. Since Beam's file support does not currently support
> this concept, the latest versions of files are always the ones returned.
> Users should be able to specify that they want to read a previous version of
> a file in FileIO.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
