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

Metadata keys lose case #26123

Closed
skhilliard opened this issue Jun 6, 2023 · 3 comments
Closed

Metadata keys lose case #26123

skhilliard opened this issue Jun 6, 2023 · 3 comments
Assignees
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. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Storage Storage Service (Queues, Blobs, Files)

Comments

@skhilliard
Copy link

  • @azure/storage-blob:
  • 12.14.0:
  • debian/linux:
  • nodejs
    • 18.14.2:
      Describe the bug
      Keys for metadata associated with blob lose their "case". E.g. camelCase becomes camelcase.
// set the blob's metadata
const metadata = {
    siteId: siteId,
    encounterId: encounterId,
    description: description,
    uploadedBy: uploadedBy,
    uploadedAt: new Date(uploadedAt).toISOString()
};

blobService
    .getContainerClient(setting.container)
    .getBlockBlobClient(blobName)
    .uploadStream(stream, blobSize, 5, { metadata })
    .then(() => {

Note 'encounterId', 'siteId', 'uploadedAt', etc.
image

Becomes
image

Expected behavior
The case of the keys would be the same instead of being made lowercase

@github-actions github-actions bot 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. needs-team-triage Workflow: This issue needs the team to triage. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Storage Storage Service (Queues, Blobs, Files) labels Jun 6, 2023
@xirzec
Copy link
Member

xirzec commented Jun 7, 2023

I think this is a duplicate of #8117

@xirzec xirzec removed the needs-team-triage Workflow: This issue needs the team to triage. label Jun 7, 2023
@github-actions github-actions bot added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Jun 7, 2023
@skhilliard
Copy link
Author

@xirzec Yeah...it does appear to be a duplicate...and I did just notice this warning...

image

...feel free to close this if you like.

Thanks,
Kelly

@xirzec
Copy link
Member

xirzec commented Jun 7, 2023

@skhilliard Closing this one as duplicate, but please let us know if you are unable to accomplish your scenario (by adding a comment on the other issue or reopening this one!)

@xirzec xirzec closed this as not planned Won't fix, can't repro, duplicate, stale Jun 7, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Sep 5, 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. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

No branches or pull requests

3 participants