search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.22k stars 21.37k forks source link

The .NET6 for Spark is WIP and .NET for Spark 3.3 commitment #105466

Closed GeorgeS2019 closed 4 months ago

GeorgeS2019 commented 1 year ago

The document needs to reflect that there is a renew commitment to update .NET for Spark to .NET6 and there is a commitment to support Spark 3.3

This will avoid Azure Synapse from loosing .NET companies and users <= Urgent

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

YashikaTyagii commented 1 year ago

@GeorgeS2019 Thanks for your feedback! We will investigate and update as appropriate.

Naveenommi-MSFT commented 1 year ago

@GeorgeS2019 Thank you for bringing this to our attention. I've delegated this to content author @ekote, who will review it and offer their insightful opinions.

ekote commented 1 year ago

Got it, thanks @Naveenommi-MSFT and @GeorgeS2019.

@GeorgeS2019, please update me (thru tagging) once the ETA to support microsoft-spark-3-3.jar for .NET 6 will be determined.

GeorgeS2019 commented 1 year ago

@ekote Could someone let me know who is the PM for .NET for Spark. Many users are very concerned if there is a serious commitment. The blocking issue e.g. BinaryFormater, which exists since Dec 2020, remains unsolved.

If the issue since Dec 2020 remains unsolved, many of us lack confidence the future of .NET for Spark,.

ekote commented 1 year ago

@GeorgeS2019 I'm sorry I don't have the details on who the PM for .NET for Spark is, or if there is any.

GeorgeS2019 commented 1 year ago

@ekote, thx, I suspected. I ask other PM

bandersmsft commented 4 months ago

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close