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

tutorial azure synapse spark pool SQL is bad gives error ClassCastException: class java.lang.Long cannot be cast to class java.lang.Integer #106122

Closed sekhemrekhutawysobekhotep closed 4 months ago

sekhemrekhutawysobekhotep commented 1 year ago

on tutorial step

https://learn.microsoft.com/en-us/azure/synapse-analytics/get-started-analyze-sql-pool#load-the-nyc-taxi-data-into-sqlpool1

the SQL fails with error

Started executing query at Line 1 (0 record affected)

HdfsBridge::recordReaderFillBuffer - Unexpected error encountered filling record reader buffer: ClassCastException: class java.lang.Long cannot be cast to class java.lang.Integer (java.lang.Long and java.lang.Integer are in module java.base of loader 'bootstrap') Total execution time: 00:00:08.247

Please fix your SQL used in this tutorial on this step I have successfully walked through all steps starting from the parent tutorial which is at following links

https://learn.microsoft.com/en-us/azure/synapse-analytics/get-started-create-workspace

https://learn.microsoft.com/en-us/azure/synapse-analytics/get-started-analyze-sql-on-demand

https://learn.microsoft.com/en-us/azure/synapse-analytics/get-started-analyze-spark


Document Details

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

AjayBathini-MSFT commented 1 year ago

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

RamanathanChinnappan-MSFT commented 1 year ago

@sekhemrekhutawysobekhotep

I've delegated this to @saveenr , a content author, to review and share their valuable insights.

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