Open BuzzCutNorman opened 3 months ago
@BuzzCutNorman do you know if this is still an issue?
Just checked 0.12.2 without a work around and got the same error:
20:30:38 Finished running 1 table model, 1 project hook in 0 hours 0 minutes and 3.27 seconds (3.27s).
20:30:39
20:30:39 Completed with 1 error and 0 warnings:
20:30:39
20:30:39 Database Error in model data_quality__eligibility_death_flag (models\data_quality\dqi\intermediate\atomic_checks\claims\eligibility\data_quality__eligibility_death_flag.sql)
operator does not exist: boolean = integer
LINE 23: when m.death_flag in (1,0) then 'valid'
^
HINT: No operator matches the given name and argument types. You might need to add explicit type casts.
Describe the bug - Required The
data_quality__eligibility_death_flag
check causes a comparison error when run on PostgreSQL. PostgreSQL will only allow boolean to be compared with data types of boolean and str. Here is a link that explains in more detail.https://www.postgresql.org/docs/current/datatype-boolean.html
I am also assuming that in the input layer eligibility definition that boolean mean the boolean type for the datawarehouse platform. Looking at the query for the death flag check I could have assumed incorrectly, and I should be converting the boolean columns to int of only 1 or 0.
Environment - Required
To Reproduce Steps to reproduce the behavior: I executed
dbt run
withclaims_enabled: true
set in thedbt_project.yml
:Expected behavior The data quality checks would run without encountering any PostgreSQL operator errors..
Screenshots If applicable, add screenshots to help explain your problem.
Additional context