Error while loading data into the dedicated sql pool

[ZaarourOmar]

Hi there,

Please note that after following your steps, creating the table in the dedicated pool and copying data into it from the parquet file shows this error 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')

I'm assuming something changed with the mapping from the file to the SQL table that needs your attention.

Thanks

Document Details

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

• ID: da9820f3-e186-4f52-7492-cb936823ea80
• Version Independent ID: 2746ca67-f71e-85c6-f5b3-0f828bcbbc68
• Content: Tutorial: Get started analyze data with dedicated SQL pools - Azure Synapse Analytics
• Content Source: articles/synapse-analytics/get-started-analyze-sql-pool.md
• Service: synapse-analytics
• Sub-service: sql
• GitHub Login: @saveenr
• Microsoft Alias: saveenr

[RamanathanChinnappan-MSFT]

@ZaarourOmar

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

[Naveenommi-MSFT]

@ZaarourOmar I've delegated this to content author @saveenr, who will review it and offer his insightful opinions.

[kenjzheng]

Temp solution is like this to create table automatically. Changing aggregate script in the tutorial to use corresponding columns. COPY INTO dbo.NYCTaxiTripSmall FROM 'https://xxx.dfs.core.windows.net/xxx/NYCTripSmall.parquet' WITH ( FILE_TYPE = 'PARQUET' ,MAXERRORS = 0 ,IDENTITY_INSERT = 'OFF' ,AUTO_CREATE_TABLE = 'ON' )

[Trace-Elements0]

I'm also getting this issue on the import step Load the NYC Taxi Data into SQLPOOL1

The solution above did not fix it for me, but the error message changed.

I now get: "Arithmetic overflow error converting expression to data type int. The statement has been terminated."

[bandersmsft]

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