dbt error: Data too long for column at row 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ01-22-2025 07:47 AM
Hi there!
We are experiencing a Databricks error we donโt recognise when we are running one of our event-based dbt models in dbt core (version 1.6.18). The dbt model uses the โinsert_by_periodโ materialisation that is still experimental for version 1.6.18.
The error message states:
Error during request to server: (conn=4757514) Data too long for column 'session_data' at row 1
We could narrow down the timeframe of the events in which this error occurs but not the error itself, since there is no column called โsession_dataโ . Has anyone encountered the same error before and knows what the issue might be?
We hope that we wonโt get the same error message again once we have upgraded to dbt version 1.9.1, since the โinsert_by_periodโ period wonโt be experimental anymore but it would be good to get to the bottom of this until then.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ01-25-2025 10:46 PM
This KB https://kb.databricks.com/metastore/data-too-long-for-column documents the cause and solution.
Can you please check the table definition if session_data is an implicit column added.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ01-27-2025 01:27 AM
Hi there! Thank you for your reply and the link, I'll take a look.
Unfortunately, session_data isn't an implicit column either.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ01-31-2025 10:47 PM
Can you please try if you are seeing this error with the latest dbt version?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ02-03-2025 01:42 AM
We are yet to upgrade dbt core to the latest version but will check again once we have done so.

