[
https://issues.apache.org/jira/browse/BEAM-2572?focusedWorklogId=350088&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-350088
]
ASF GitHub Bot logged work on BEAM-2572:
----------------------------------------
Author: ASF GitHub Bot
Created on: 26/Nov/19 22:23
Start Date: 26/Nov/19 22:23
Worklog Time Spent: 10m
Work Description: pabloem commented on issue #9955: [BEAM-2572] Python
SDK S3 Filesystem
URL: https://github.com/apache/beam/pull/9955#issuecomment-558843630
@MattMorgis @tamera-lanham There seems to be an issue with the fake client :
) would love to move this forward.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 350088)
Time Spent: 2.5h (was: 2h 20m)
> Implement an S3 filesystem for Python SDK
> -----------------------------------------
>
> Key: BEAM-2572
> URL: https://issues.apache.org/jira/browse/BEAM-2572
> Project: Beam
> Issue Type: Task
> Components: sdk-py-core
> Reporter: Dmitry Demeshchuk
> Priority: Minor
> Labels: GSoC2019, gsoc, gsoc2019, mentor, outreachy19dec
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> There are two paths worth exploring, to my understanding:
> 1. Sticking to the HDFS-based approach (like it's done in Java).
> 2. Using boto/boto3 for accessing S3 through its common API endpoints.
> I personally prefer the second approach, for a few reasons:
> 1. In real life, HDFS and S3 have different consistency guarantees, therefore
> their behaviors may contradict each other in some edge cases (say, we write
> something to S3, but it's not immediately accessible for reading from another
> end).
> 2. There are other AWS-based sources and sinks we may want to create in the
> future: DynamoDB, Kinesis, SQS, etc.
> 3. boto3 already provides somewhat good logic for basic things like
> reattempting.
> Whatever path we choose, there's another problem related to this: we
> currently cannot pass any global settings (say, pipeline options, or just an
> arbitrary kwarg) to a filesystem. Because of that, we'd have to setup the
> runner nodes to have AWS keys set up in the environment, which is not trivial
> to achieve and doesn't look too clean either (I'd rather see one single place
> for configuring the runner options).
> Also, it's worth mentioning that I already have a janky S3 filesystem
> implementation that only supports DirectRunner at the moment (because of the
> previous paragraph). I'm perfectly fine finishing it myself, with some
> guidance from the maintainers.
> Where should I move on from here, and whose input should I be looking for?
> Thanks!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
