[Bug] String/List Agg Fields in Connector Status model result in error if they exceed limits

[fivetran-joemarkiewicz]

Is there an existing issue for this?

• [X] I have searched the existing issues

Describe the issue

It has been reported by a number of users that the following fields in the fivetran_platform__connector_status model have the potential to result in a runtime failure if the string/list agg is too long and exceeds the limits. This has been reported on Postgres, Redshift, and Snowflake warehouses:

• errors_since_last_completed_sync
• warnings_since_last_completed_sync

I had considered the following approaches to address this error:

• ❌ Truncate the string/list agg if it is too long. However, I did not like this approach as while this would result in success, it would be truncating the data without the customer knowing. That would not be an ideal solution.
• 🤔 Fully remove the problematic fields. This is a viable option and we already remove these fields for sql server. However, I would like to explore a better solution without removing these fields entirely.
• 👷 Changing the form and function of these fields to be metrics as opposed to string/list agg. I currently like this solution the best as we don't remove the fields and just change their use to ideally be more useful for all customers and the names will be more consistent. I will explore building this out first. If this is not successful then I will switch to the option of removing the fields entirely.

Relevant error log or model output

Error: String '(LISTAGG result)' is too long and would be truncated

Expected behavior

The transformation run does not result in failure

dbt Project configurations

Quickstart

Package versions

v1.6.0

What database are you using dbt with?

postgres, redshift, snowflake

dbt Version

1.7.1

Additional Context

Are you willing to open a PR to help address this issue?

• [ ] Yes.
• [ ] Yes, but I will need assistance and will schedule time during our office hours for guidance
• [ ] No.

[fivetran-joemarkiewicz]

This has been addressed in the recent release. As such, closing out this issue.