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

Azure storage table sdk seems not supported #5655

Closed
ruowan opened this issue Oct 18, 2019 · 24 comments
Closed

Azure storage table sdk seems not supported #5655

ruowan opened this issue Oct 18, 2019 · 24 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. feature-request This issue requires a new behavior in the product in order be resolved. Tables

Comments

@ruowan
Copy link
Member

ruowan commented Oct 18, 2019

I don't find Azure storage table. Where is SDK I can use it for azure storage table?

@ramya-rao-a ramya-rao-a added Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files) labels Oct 18, 2019
@ramya-rao-a ramya-rao-a added Service Attention Workflow: This issue is responsible by Azure service team. triage labels Oct 18, 2019
@ghost
Copy link

ghost commented Oct 18, 2019

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

@XiaoningLiu
Copy link
Member

Hi, table is only available in legacy Node.js SDK package “azure-storage”

@pacific202
Copy link
Contributor

Does this mean that Table Storage is going away?

@XiaoningLiu
Copy link
Member

XiaoningLiu commented Oct 22, 2019

No. Table Storage will still be there, new Table SDK is not planned yet.

@pacific202
Copy link
Contributor

So Table Storage won't be fully supported. This seems to me as though Table Storage would not be a good design choice for new applications, and I'll be looking to migrate my existing apps to something else.

@HarshaNalluru HarshaNalluru added the customer-reported Issues that are reported by GitHub users external to the Azure organization. label Oct 23, 2019
@XiaoningLiu
Copy link
Member

@dineshmurthy

@andreujuanc
Copy link

I don't want to be harsh on anyone, but, few weeks ago I found that the new SDK for Service Bus is very poor, feature wise. And now I find myself in the same spot while trying to query table storage data that has been saved there by another Microsoft product.

I find this very disconcerting.

Personally I like the new SDK's design, but I often have to resolve to Rest APIs to interact with azure. :(

@pacific202
Copy link
Contributor

Note to Azure folks who might be reading this issue...

This is the sort of thing that makes an architect start to evaluate AWS and GCP for migration away from Azure.

@Petermarcu
Copy link
Member

We are planning to have an updated version of the Tables libraries that aligns with the Azure SDK guidelines as we have with Blobs, Files, and Queues so far. We aren't at a point where we know concrete dates but we hope to be able to share more in the next couple months and follow that with some previews.

@vinjiang vinjiang added the feature-request This issue requires a new behavior in the product in order be resolved. label Feb 11, 2020
@ahuggins-nhs
Copy link

We are planning to have an updated version of the Tables libraries that aligns with the Azure SDK guidelines as we have with Blobs, Files, and Queues so far. We aren't at a point where we know concrete dates but we hope to be able to share more in the next couple months and follow that with some previews.

Git 'er done! This is not a show stopper for our team, as we are promisifying the old library for tables, but it would be nice to drop support for azure-storage library ASAP.

@mpth
Copy link

mpth commented Apr 28, 2020

This feels death by a 1000 paper cuts. Maybe I'm just unlucky and I always use the parts of Azure that are getting very little love. Please fix this gap sooner rather than later.

@JonSilver
Copy link

I agree. This is a ridiculous situation where nobody seems to own the problem. Time passes, nothing happens. Folks ask, you say "use v2" or "we're talking about it" or even worse "use v12" to which the answer is, of course, "no table storage". In other words, anyone asking just gets the brush-off - "go away and stop bothering us". Someone needs to take charge, assign a team, architect and design the thing, and make it happen. What's the hold up? Did you all just forget to take table storage with you on the SDK journey?

We (Gold Partners, developers) need to use table storage for new solutions. Wrapping requests just to use promises is clunky. The Request JS library is deprecated. Its incredibly hard justifying use of table storage to clients because of all this, because it looks like it's a threatened technology that Microsoft is going to drop. It's been way too long since all the other storage SDKs moved on and tables got left behind. We're all trying to just do our jobs - so give us something we can work with.

@Petermarcu
Copy link
Member

Work on Tables is has started. We are hoping to have previews in a couple months.

@Petermarcu Petermarcu added Cosmos and removed Storage Storage Service (Queues, Blobs, Files) labels Apr 30, 2020
@ghost
Copy link

ghost commented Apr 30, 2020

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @kushagraThapar, @srinathnarayanan, @southpolesteve, @shurd, @ealsur, @j82w, @anfeldma-ms.

@JonSilver
Copy link

JonSilver commented Apr 30, 2020

Work on Tables is has started. We are hoping to have previews in a couple months.

Thank you for the update, @Petermarcu. It's probably worth 15 minutes of someone's time to spread this piece of excellent news around the various places where table storage support has been discussed. Apart from the code itself, clear consistent communication around js table storage support has been the rarest commodity.

@shaman-apprentice
Copy link

#4573 and this one are duplicates aren't they?

@southpolesteve southpolesteve removed the Service Attention Workflow: This issue is responsible by Azure service team. label Jul 14, 2020
@ghost ghost added the needs-team-triage Workflow: This issue needs the team to triage. label Jul 14, 2020
@southpolesteve southpolesteve removed the needs-team-triage Workflow: This issue needs the team to triage. label Jul 14, 2020
@ramya-rao-a ramya-rao-a added this to the Backlog milestone Jul 16, 2020
@ramya-rao-a ramya-rao-a added Tables and removed Cosmos labels Jul 16, 2020
@ramya-rao-a ramya-rao-a modified the milestones: Backlog, [2020] August Jul 16, 2020
@ramya-rao-a ramya-rao-a assigned joheredi and unassigned XiaoningLiu Jul 16, 2020
@ramya-rao-a
Copy link
Contributor

Hello all,

Just adding an update here that we will be releasing the first preview next month.

Thanks for your patience!

@mpth
Copy link

mpth commented Jul 16, 2020

Great news - thanks for the update!

@ahuggins-nhs
Copy link

@jostein-skaar
Copy link

@ahuggins-nhs
Copy link

@joheredi
Copy link
Member

Hello everyone! We are happy to announce that we have released the first Beta of the new Azure Tables SDK. It conforms to our new guidelines on writing JS SDKs for Azure services which ensure it will remain idiomatic, consistent and diagnosable.

You can install it with npm install @azure/data-tables

Please share your feedback on the new design at #11179 and/or report any problems you find in a new GitHub issue. Looking forward to hear from you!

@mpth
Copy link

mpth commented Sep 10, 2020

@joheredi looks promising 🙂

@joheredi
Copy link
Member

Hi Everyone! We are happy to announce that the new stable version (12.0.0) of @azure/datat-tables has been released. You can install it with npm install @azure/data-tables

For more details please see the README.

If you have any questions or feedback, please log an issue here

@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. feature-request This issue requires a new behavior in the product in order be resolved. Tables
Projects
None yet
Development

No branches or pull requests