[
https://issues.apache.org/jira/browse/BEAM-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758248#comment-16758248
]
Jeff Klukas commented on BEAM-4822:
-----------------------------------
It's unfortunate that we're going to end up stuffing info from a typed
filesystem-specific metadata object into a map of strings, but I think I'm
coming around to that being the pragmatic thing to do. I agree with you that
concepts like object version are not firmly enough established that we can
reasonably expect a compatible interface across storage providers.
And the benefit of not having to worry about coder compatibility as we add new
keys is definitely attractive for being able to evolve what attributes we
capture per filesystem.
> 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)
