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

expect_table_columns_to_match_ordered_list is failing on Redshift #99

Closed
mirosval opened this issue Jul 21, 2021 · 1 comment · Fixed by #101
Closed

expect_table_columns_to_match_ordered_list is failing on Redshift #99

mirosval opened this issue Jul 21, 2021 · 1 comment · Fixed by #101
Labels
bug Something isn't working

Comments

@mirosval
Copy link
Contributor

After the upgrade to 0.4 the expectation is failing on Redshift with

Invalid operation: failed to find conversion function from "unknown" to text;

I think this is because redshift cant guess the type of the ordered_column_names and ordered_relation_column_names. Locally I managed to get it to run by adding ::text after.

select
  count(*) as failures,
  count(*) != 0 as should_warn,
  count(*) != 0 as should_error
from (
       with test_data as (

         select
           'COL_A, COL_B'::text as ordered_column_names,
           'COL_A, COL_B'::text as ordered_relation_column_names

       )
       select *
       from test_data
       where ordered_column_names != ordered_relation_column_names

     ) dbt_internal_test
@clausherther
Copy link
Contributor

Thanks for raising this issue @mirosval ! Interesting, I'll check into this as much as I can, as well as the other issues you've opened. We don't officially support Redshift because we don't have a way to test against a RS cluster. But maybe there are some generic things we can do help with types etc that would also work on Redshift. I'll take a look by end of the week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants