Skip to content
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] Incompatible join condition within recharge__billing_history #23

Open
1 of 4 tasks
fivetran-joemarkiewicz opened this issue Jan 9, 2025 · 1 comment
Open
1 of 4 tasks
Labels
error:forced type:bug Something is broken or incorrect

Comments

@fivetran-joemarkiewicz
Copy link
Collaborator

Is there an existing issue for this?

  • I have searched the existing issues

Describe the issue

It seems that in some cases there can be an error in the recharge__billing_history model where a join condition is not working as expected. In fact it seems that one of the datatypes is interpreted as a boolean. We can likely address this issue by ensuring all fields which we decide to join on are of the same datatype. This should likely be done at the staging model level. We should trace back the fields we join on and ensure the datatypes are consistent at the staging model layer.

Relevant error log or model output

Database Error in model recharge__billing_history (models/recharge__billing_history.sql)
No matching signature for operator = for argument types: INT64, BOOL

Input types for : {INT64, BOOL} at [57:23]

Expected behavior

The model is able to run as expected and the datatypes for joins are consistent.

Possible solution

See my note in the description.

dbt Project configurations

Default

Package versions

Latest

What database are you using dbt with?

bigquery

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.
@fivetran-joemarkiewicz fivetran-joemarkiewicz added type:bug Something is broken or incorrect error:forced labels Jan 9, 2025
@fivetran-jamie
Copy link
Contributor

This has been tied back to a connector issue. We will close this out once that is resolved within Fivetran

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
error:forced type:bug Something is broken or incorrect
Projects
None yet
Development

No branches or pull requests

2 participants