Writing output into AWS S3 does not work
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 197
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
I understand dbeam officially does not support S3. I kinda of hopping it might work out of the box because Beam supports S3 as its file io. However I got the following error:
"No filesystem found for scheme s3"
Do you have a clue why is this happening? Do you plan to add S3 output in the future?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or dbeam entry points. First inspect how dbeam configures Apache Beam file output and verify the available S3 filesystem support; done would require a defined implementation scope and confirmation that S3 output is supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100