You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I have built a simple effectivity satellite for a link with 2 hubs, and it does not appear to be loading the way I expect it. I set up test data for 5 rows (each with a different effective date, i.e., one row loaded per run). In the test data, the value for hub_1 was constant, and the value for hub_2 varied. After 5 loads there are 5 rows in the link and 5 rows in the effectivity satellite. The definition of the effectivity satellite is:
Each row in the effectivity satellite has an end date of '9999-12-31' (see screenshots), but I was expecting that only the last (most recent based on DV_APPDT) row should have that end date, the other rows should have an end date identifying when the next most recent row superseded it.
Is this a bug ,or did I set up the effectivity satellite wrong, or are my expectations incorrect, or (something else)?
To Reproduce
execute 'dbt run --select "+link_hub_links +sate_hub_links"' 5 times, changing the load date value between each run. I can provide a copy of the dbt project, if required
Expected behavior
See above in "Describe the bug"
Screenshots
The data in the effectivity satellite (sate_hub_links):
Yes, I completely missed that option in the documentation. I added that to configuration for the satellite and regenerated it. At first glance, there were more rows added to the satellite than I expected, but when you consider the 'insert-only' data vault 'rule', the data makes sense.
Thanks for the pointer, @DVAlexHiggs. I will close this issue.
Describe the bug
I have built a simple effectivity satellite for a link with 2 hubs, and it does not appear to be loading the way I expect it. I set up test data for 5 rows (each with a different effective date, i.e., one row loaded per run). In the test data, the value for hub_1 was constant, and the value for hub_2 varied. After 5 loads there are 5 rows in the link and 5 rows in the effectivity satellite. The definition of the effectivity satellite is:
Each row in the effectivity satellite has an end date of '9999-12-31' (see screenshots), but I was expecting that only the last (most recent based on DV_APPDT) row should have that end date, the other rows should have an end date identifying when the next most recent row superseded it.
Is this a bug ,or did I set up the effectivity satellite wrong, or are my expectations incorrect, or (something else)?
Thanks in advance,
Environment
dbt version: 1.7.16
automate_dv version: 0.11.0
Database/Platform: Snowflake (dbt adpater v1.7.5)
To Reproduce
execute 'dbt run --select "+link_hub_links +sate_hub_links"' 5 times, changing the load date value between each run. I can provide a copy of the dbt project, if required
Expected behavior
See above in "Describe the bug"
Screenshots
The data in the effectivity satellite (sate_hub_links):
The data in link (link_hub_links):
Log files
N/A
Additional context
N/A
AB#5471
The text was updated successfully, but these errors were encountered: