[Bug] Add chunk_index to the unique_id in the rag__unified_document end model

[fivetran-joemarkiewicz]

Is there an existing issue for this?

• I have searched the existing issues

Describe the issue

At the moment the unique_id field has the possibility of not truly being unique if there are multiple chunks associated with a document. Therefore, there is a chance where the uniqueness fails and the key is no longer unique.

Relevant error log or model output

Uniqueness test fails and the unique key is not truly unique to the individual row.

Expected behavior

The field is truly unique to the chunk.

Possible solution

Add chunk_index to this code update here in order to properly have a true unique field to the individual row.

In addition to the above code change we will also need to update the documentation here to account for the new field factored into the surrogate key.

dbt Project configurations

Default.

Package versions

Latest

What database are you using dbt with?

postgres, redshift, snowflake, bigquery, databricks

How are you running this dbt package?

Fivetran Quickstart Data Model

dbt Version

Latest

Additional Context

No response

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

• Yes.
• Yes, but I will need assistance.
• No.