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

DM-46340: Fix query datasets failing when run collection specified #1079

Merged
merged 3 commits into from
Sep 16, 2024

Conversation

dhirving
Copy link
Contributor

@dhirving dhirving commented Sep 13, 2024

Checklist

  • ran Jenkins
  • added a release note for user-visible changes to doc/changes
  • (if changing dimensions.yaml) make a copy of dimensions.yaml in configs/old_dimensions

Copy link

codecov bot commented Sep 13, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.69%. Comparing base (da89c37) to head (1582b9e).
Report is 4 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1079   +/-   ##
=======================================
  Coverage   89.69%   89.69%           
=======================================
  Files         360      360           
  Lines       47041    47054   +13     
  Branches     9659     9660    +1     
=======================================
+ Hits        42193    42206   +13     
  Misses       3480     3480           
  Partials     1368     1368           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@dhirving dhirving marked this pull request as ready for review September 13, 2024 22:48
Copy link
Member

@TallJimbo TallJimbo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great. I'm glad casting the literals worked, because it would have been a pain to try to make the code that applies any_value aware of what is and is not a literal.

Fix an issue where query_datasets would fail on Postgres 16 with the error 'psycopg2.errors.DatatypeMismatch: could not determine polymorphic type because input has type unknown'.

This was occurring because a run collection name string literal was appearing in an any_value aggregate function without a type defined.
Fix an issue similar to the previous commit, where query_datasets would fail on Postgres 16 with the error 'psycopg2.errors.DatatypeMismatch: could not determine polymorphic type because input has type unknown'.

This was occurring when there was a single collection specified for the dataset search, causing a literal  "collection" dataset field value to be included in an any_value aggregate function.
@dhirving dhirving merged commit 4a59ea5 into main Sep 16, 2024
18 checks passed
@dhirving dhirving deleted the tickets/DM-46340 branch September 16, 2024 16:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants