beam-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <>
Subject [jira] [Work logged] (BEAM-12435) Generalize S3FileSystem
Date Tue, 13 Jul 2021 12:10:00 GMT


ASF GitHub Bot logged work on BEAM-12435:

                Author: ASF GitHub Bot
            Created on: 13/Jul/21 12:09
            Start Date: 13/Jul/21 12:09
    Worklog Time Spent: 10m 
      Work Description: aromanenko-dev commented on pull request #15036:

   @mattrudary Thanks for your contribution! Are you going to replicate these changes to `aws2`
module as well?

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail:

For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 621960)
    Time Spent: 3h 20m  (was: 3h 10m)

> Generalize S3FileSystem
> -----------------------
>                 Key: BEAM-12435
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-aws
>            Reporter: Matt Rudary
>            Assignee: Matt Rudary
>            Priority: P2
>              Labels: aws, aws-s3
>             Fix For: 2.32.0
>          Time Spent: 3h 20m
>  Remaining Estimate: 0h
> I'm working with multiple storage systems that speak the S3 api. I would like to support
FileIO operations for these storage systems, but S3FileSystem hardcodes the s3 scheme (the
various systems use different URI schemes) and it is in any case impossible to instantiate
more than one in the current design.
> I'd like to refactor the code in (and maybe
somewhat to enable this use-case. I haven't worked out the details yet, but it will take some
thought to make this work in a non-hacky way.

This message was sent by Atlassian Jira

View raw message