v0.1.0-a2 dbt_unified_rag

PR #7 includes the following updates:

Bug Fixes

• For Snowflake destinations, we have removed the post-hook from the rag__unified_document which generated the rag__unified_search Cortex Search Service.
  • While the Search Service worked when deployed locally, there were issues identified when deploying and running via Fivetran Quickstart. In order to ensure Snowflake users are still able to take advantage of the rag__unified_document end model, we have removed the Search Service from execution until we are able to verify it works as expected on all supported orchestration methods.
  • If you would like, you can generate your own Snowflake Cortex Search Service by following the Create Cortex Search Service guidelines provided by Snowflake. For additional assistance, you can structure your Cortex Search Service off of the below query to effectively leverage the rag__unified_document generated from this data model.

  -- Cortex Search Service created using the rag__unified_document model
  
  create cortex search service if not exists <your_schema>.<your_new_search_service_name>
      on chunk
      attributes unique_id
      warehouse = <your_warehouse>
      target_lag = '1 days' --You can specify this to your liking
      as (
          select * from rag__unified_document
      )

Under the Hood

• Adjusted the cluster_by configuration within the dbt__unified_rag to cluster by the update_date (previously unique_id) for improved Snowflake performance.

Full Changelog: v0.1.0-a1...v0.1.0-a2