New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Save test history fails when a model and a source have the same name with a dependency between them #371
Labels
bug
Something isn't working
Comments
akshaykarle
added a commit
to akshaykarle/dbt-re-data
that referenced
this issue
Nov 2, 2022
…with the same name * Without checking the node_type, a model could match a source with the same name and the macro would error out trying to get the database on that node which is not present for a source * Fixes issue: re-data/re-data#371
akshaykarle
added a commit
to akshaykarle/dbt-re-data
that referenced
this issue
Nov 2, 2022
…with the same name * Without checking the node_type, a model could match a source with the same name and the macro would error out trying to get the database on that node which is not present for a source * Fixes issue: re-data/re-data#371
akshaykarle
added a commit
to akshaykarle/dbt-re-data
that referenced
this issue
Nov 2, 2022
…with the same name * Without checking the node_type, a model could match a source with the same name and the macro would error out trying to get the database on that node which is not present for a source * Fixes issue: re-data/re-data#371
re-data/dbt-re-data#106 should fix this. is someone able to review and merge it? it has been open for a while now. |
akshaykarle
added a commit
to akshaykarle/dbt-re-data
that referenced
this issue
Jun 21, 2023
…with the same name * Without checking the node_type, a model could match a source with the same name and the macro would error out trying to get the database on that node which is not present for a source * Fixes issue: re-data/re-data#371
akshaykarle
added a commit
to akshaykarle/dbt-re-data
that referenced
this issue
Jun 21, 2023
…with the same name * Without checking the node_type, a model could match a source with the same name and the macro would error out trying to get the database on that node which is not present for a source * Fixes issue: re-data/re-data#371
cmardiros
pushed a commit
to cmardiros/dbt-re-data
that referenced
this issue
Jun 21, 2023
…with the same name * Without checking the node_type, a model could match a source with the same name and the macro would error out trying to get the database on that node which is not present for a source * Fixes issue: re-data/re-data#371
cmardiros
pushed a commit
to cmardiros/dbt-re-data
that referenced
this issue
Jun 21, 2023
…with the same name * Without checking the node_type, a model could match a source with the same name and the macro would error out trying to get the database on that node which is not present for a source * Fixes issue: re-data/re-data#371
akshaykarle
added a commit
to akshaykarle/dbt-re-data
that referenced
this issue
Jun 21, 2023
…with the same name * Without checking the node_type, a model could match a source with the same name and the macro would error out trying to get the database on that node which is not present for a source * Fixes issue: re-data/re-data#371
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When
re_data:save_test_history
is enabled,dbt test
command fails with the following error:Expected behavior
dbt test
should complete without any errors and does so whenre_data:save_test_history
isfalse
.To Reproduce
Steps to reproduce the behavior:
foobar
.dbt_utils.equal_rowcount
betweenref('foobar')
and usesource('hello', 'foobar')
as thecompare_model
.re_data:save_test_history
totrue
and rundbt test
.Screenshots
NA
Logs and additional context
NA
The text was updated successfully, but these errors were encountered: