Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an S3Uri convenience class #395

Closed
1 task done
ianbotsf opened this issue Nov 1, 2021 · 1 comment
Closed
1 task done

Add an S3Uri convenience class #395

ianbotsf opened this issue Nov 1, 2021 · 1 comment
Labels
feature-request A feature should be added or improved. no-auto-closure We do not want this issue to be automatically closed.

Comments

@ianbotsf
Copy link
Contributor

ianbotsf commented Nov 1, 2021

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue, please leave a comment

Describe the Feature

S3 objects are identified by (at least) a bucket and a key but may also be identified by an S3 URI (e.g., s3://bucket/path/to/object). These URIs are convenient for storing, passing, and utilizing in other services (e.g., EMR). Construction and parsing of these URIs, however, is left to users to implement.

Other SDKs (e.g., Java v1) implement convenience classes that represent S3 URIs and provide conversions to/fro.

Is your Feature Request related to a problem?

Merely the problem of reducing boilerplate and increasing development speed.

Proposed Solution

Add an S3Uri class which parses/wraps the properties of an S3 object.

Describe alternatives you've considered

None so far.

Additional Context

  • I may be able to implement this feature request
@ianbotsf ianbotsf added feature-request A feature should be added or improved. needs-triage This issue or PR still needs to be triaged. labels Nov 1, 2021
@aajtodd aajtodd removed the needs-triage This issue or PR still needs to be triaged. label Nov 2, 2021
@ianbotsf ianbotsf added the no-auto-closure We do not want this issue to be automatically closed. label Jul 11, 2022
@RanVaknin RanVaknin closed this as not planned Won't fix, can't repro, duplicate, stale Dec 12, 2024
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request A feature should be added or improved. no-auto-closure We do not want this issue to be automatically closed.
Projects
None yet
Development

No branches or pull requests

3 participants