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

Update .NET for Apache Spark - Azure Synapse Analytics to support Apache Spark 3.3.1 #105027

Closed
GeorgeS2019 opened this issue Feb 9, 2023 · 5 comments

Comments

@GeorgeS2019
Copy link

GeorgeS2019 commented Feb 9, 2023

Topic 1 (Urgent)

The .NET Core 3.1 library has reached end of support and therefore has been removed from the Azure Synapse Runtime for Apache Spark 3.3, meaning users will no longer be able to access Spark APIs through C# and F# and execute C# code in notebooks and through jobs.

This would mean Use .NET for Apache Spark - Azure Synapse Analytics this page is no longer officially support.

Please work with the .NET for Apache Spark to ASAP migrate from the .NET Core 3.1 library in existing .NET for Apache Spark to .NET6

Topic 2

Azure Synapse Runtime for Apache Spark 3.3 is now in Public Preview

Support for spark v3.3.1

Topic 3

How to use the .NET for Apache Spark Delta Extension to read a delta table?

Document Details

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

@ManoharLakkoju-MSFT
Copy link
Contributor

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

@JohnDietrich-Pepper
Copy link

Seconding the need to help .NET for Spark to update to 6.0

@Naveenommi-MSFT
Copy link
Contributor

Hi @juluczni
Could you please review add comments on this, update as appropriate.

@Naveenommi-MSFT
Copy link
Contributor

Naveenommi-MSFT commented Feb 13, 2023

@GeorgeS2019
I've delegated this to content author @juluczni, who will review it and offer their insightful opinions.

@bandersmsft
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants