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.

Sign up for GitHub

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

Jump to bottom

Is there a migration guide from v11 SDK's "Microsoft.Azure.Storage.DataMovement.TransferManager"? #20828

Closed
mgroetan opened this issue May 4, 2021 · 5 comments
Closed

Is there a migration guide from v11 SDK's "Microsoft.Azure.Storage.DataMovement.TransferManager"? #20828

mgroetan opened this issue May 4, 2021 · 5 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. 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 Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)

Comments

@mgroetan
Copy link

mgroetan commented May 4, 2021

Query/Question
We're using the "Microsoft.Azure.Storage.DataMovement.TransferManager" class in the v11 SDK to handle vast amounts of file copying between local disk and BLOB storage. This is a very integral part of our solution, and the current implementation is working quite well, even though we've had to implement some checksum/retry logic.

We're "of course" in the process of migrating to the new v12 SDK, and are having good progress on the "regular" BLOB handling elsewhere, through the "Azure.Storage.Blobs" package.
But we struggle to see a clear migration path for the "TransferManager" functionality. Can you point us in the right direction?

Environment:

  • Name and version of the Library package used: Azure.Storage.Blobs 12.8.3
  • Hosting platform or OS and .NET runtime version: Azure AppService running .NET Core 3.1 and .NET Standard 2.0.
  • IDE and version : Visual Studio 16.9.4
@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels May 4, 2021
@jsquire jsquire added Client This issue points to a problem in the data-plane of the library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files) labels May 4, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label May 4, 2021
@ghost
Copy link

ghost commented May 4, 2021

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

Issue Details

Query/Question
We're using the "Microsoft.Azure.Storage.DataMovement.TransferManager" class in the v11 SDK to handle vast amounts of file copying between local disk and BLOB storage. This is a very integral part of our solution, and the current implementation is working quite well, even though we've had to implement some checksum/retry logic.

We're "of course" in the process of migrating to the new v12 SDK, and are having good progress on the "regular" BLOB handling elsewhere, through the "Azure.Storage.Blobs" package.
But we struggle to see a clear migration path for the "TransferManager" functionality. Can you point us in the right direction?

Environment:

  • Name and version of the Library package used: Azure.Storage.Blobs 12.8.3
  • Hosting platform or OS and .NET runtime version: Azure AppService running .NET Core 3.1 and .NET Standard 2.0.
  • IDE and version : Visual Studio 16.9.4
Author: mgroetan
Assignees: -
Labels:

Client, Service Attention, Storage, customer-reported, needs-team-attention, needs-triage, question
Milestone: -

@mgroetan
Copy link
Author

mgroetan commented May 5, 2021 •
edited
Loading

And as I've mentioned over in the "data movement" repo, the docs for "Transfer data" still points to the v11 SDK code examples.

@amnguye
Copy link
Member

amnguye commented May 5, 2021

There's no migration guide because the development of the next generation of the Data Movement Library is still underway.

@domedellolio
Copy link

Hi @amnguye,

Q1: is there any update regarding "the next generation of the Data Movement Library"?.
Q2: From a guidance perspective, should we still continue to use Microsoft.Azure.Storage.DataMovement?

Thanks

@kinizumi
Copy link

I believe people are abandoning this library because of deprecates, what a shame

@github-actions github-actions bot locked and limited conversation to collaborators Mar 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
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 Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@jsquire @mgroetan @domedellolio @amishra-dev @kinizumi @amnguye