[
https://issues.apache.org/jira/browse/BEAM-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757017#comment-16757017
]
Ismaël Mejía edited comment on BEAM-4822 at 1/31/19 10:50 AM:
--------------------------------------------------------------
I know this is not Beamish, but I am wondering if we should add a sort of
Map<String, String> for all the 'filesystem' extended (specific) properties.
Otherwise we will keep extending and breaking the default Coder. Additionally
we could improve the FileIO.match API to better filter based on those. Pinging
[[email protected]] because he could be interested in this too.
was (Author: iemejia):
I know this is not beamish, but I am wondering if we sould add a sort of
Map<String, String> for all the 'filesystem' extended (and specific)
properties. Otherwise we will keep working the Coders. And additionally we
could improve the FileIO.match API to better filter for those. Pinging
[[email protected]] because he could be interested in this too.
> 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)
