Streamstone icon indicating copy to clipboard operation
Streamstone copied to clipboard

Migrate from Microsoft.Azure.Cosmos.Table toAzure.Data.Tables

Open goldsam opened this issue 2 years ago • 1 comments

The Microsoft.Azure.Cosmos.Table package has been deprecated in favor of Azure.Data.Tables. Consider migrating to support Azure.Data.Tables.

goldsam avatar Jun 14 '22 03:06 goldsam

The Microsoft.Azure.Cosmos.Table package has been deprecated in favor of Azure.Data.Tables. Consider migrating to support Azure.Data.Tables.

I am not sure if you realized the actual scope of this request. I most certainly share the same sentiment, however before making that very same request I wanted to see what that would entail so in other words, I am not trying to beat you down or admonish you.

I've been going through this codebase for the last 3 days in my private repo as I wanted to port an old POC I had and get it working with the new Azure Sdk. I can assure you this is close to a fundamental re-write. The primary cause is that AzDT uses the RestClient, as well as a slew of Azure.Core objects, under the hood. EntityProperty, PropertyMap, EntityProperties, Incudes, TableEntity, EntityOperation, TableOperation and many more would need to be completely removed or re-tooled. You can get a better idea of how I made those deductions by reading into the migration guide if you have not already: https://github.com/Azure/azure-sdk-for-net/blob/Azure.Data.Tables_12.6.1/sdk/tables/Azure.Data.Tables/MigrationGuide.md

That is still good news, in the sense of reducing the codebase for SS, as it was doing a lot of intercession to abstract those pesky OperationContext responsibilities away to make a clean usage of WATS as an ES. Reviewing the design and implementation guidelines the Azure Sdk Team adheres to, available here: https://azure.github.io/azure-sdk/dotnet_implementation.html, revealed to me at the very least that a lot of effort would be needed to make this package compliant; not an easy undertaking.

Impossible? Most certainly not! I have observed several repos with similar requests, so this is simply a PSA for the community members to understand what it means to make these types of requests and if it should be done.

jjhayter avatar Sep 04 '22 23:09 jjhayter

@Zer010 That's fair. However, this code base is not huge.

@yevhen Would you be open to accepting a PR if I invested the work?

goldsam avatar Oct 25 '22 19:10 goldsam

Yeah I would be happy to help on the PR

jjhayter avatar Nov 08 '22 10:11 jjhayter

@goldsam @Zer010 Hi guys! Sorry for late reply, was on vacation.

Of course, I'll be happy to accept the PR 🤗

yevhen avatar Nov 08 '22 12:11 yevhen

Has the work been done or is there a plan still to move to Azure.Data.Tables?

cbrown11 avatar Aug 31 '23 14:08 cbrown11

Nope. No plans yet. Will be happy to accept PR) If someone can concentrate all api related stuff into an abstraction for which later could be created an alternative implementation, it would be a huge step forward for resolving this issue

yevhen avatar Oct 14 '23 09:10 yevhen

@yevhen , I think https://github.com/waywedo/waywedo.Streamstone has a migration to Azure.Data.Tables, which seem to be complete. I did not test it, but you might be interested into this fork.

Greybird avatar Nov 20 '23 14:11 Greybird

Done! 3.0.0 is on nuget! Kudos to @sergiojrdotnet for the amazing work he did on this issue!

yevhen avatar Dec 02 '23 17:12 yevhen