Details
Description
Beam is moving to an unified Filesystem runtime definition allowing all input/output connectors to transparently read/write to CloudFS providers (S3, Google Storage, Azure BlobStorage) or local and HDFS-compliant filesystems
Idea is to support the same pattern for the Datastore / Dataset definitions in TCOMP
DatastoreDefinition will let the user choose the FS provider
DatasetDefinition will be relative common to all of them with a path (potentially within a bucket)
Attachments
Issue Links
- depends on
-
TCOMP-267 A component family can provide a new file system definition.
- Closed
-
TCOMP-268 A component family can provide a new file/record format definition.
- Closed
- is duplicated by
-
TCOMP-459 Rest API : Add missing endpoint for export wizard
- Closed
- prerequisite of
-
TCOMP-458 Add some semantic to have the filesystem/format notion for IO components and web service
- Closed