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

[FEATURE REQ] Support setting AccessTier when using BlockBlobClient.getBlobOutputStream() #6391

Closed
rvervaek opened this issue Nov 18, 2019 · 2 comments
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Storage Storage Service (Queues, Blobs, Files)

Comments

@rvervaek
Copy link

When I use the BlockBlobClient.getBlobOutputStream() method to upload data it is not possible to set the AccessTier for the blob.

Provide an overloaded method getBlobOutputStream() that has a parameter AccessTier, that will write the data to the blob using the provided AccessTier.

@rvervaek rvervaek changed the title Support setting AccessTier when using BlockBlobClient.getBlobOutputStream() [FEATURE REQ] [FEATURE REQ] Support setting AccessTier when using BlockBlobClient.getBlobOutputStream() Nov 18, 2019
@rickle-msft
Copy link
Contributor

@rvervaek Thank you for pointing out this oversight. We will schedule some work to add an overload that accepts accessTier, metadata, and blob http headers.

@rickle-msft rickle-msft added Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Storage Storage Service (Queues, Blobs, Files) labels Nov 18, 2019
@rickle-msft
Copy link
Contributor

I am going to close this issue as the fix has been merged.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

No branches or pull requests

2 participants