-
Notifications
You must be signed in to change notification settings - Fork 415
QoL: improve DataValidationError output: use identifying columns if present #2915
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
QoL: improve DataValidationError output: use identifying columns if present #2915
Conversation
djudjuu
commented
Jul 22, 2025
- Fixes Show offending item in logs when schema_contract is set to "freeze" #1772
✅ Deploy Preview for dlt-hub-docs canceled.
|
| for x in table_schema.get("columns", {}).values() | ||
| if x.get("primary_key") or x.get("merge_key") or x.get("unique") | ||
| ] | ||
| if identifier_columns: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i decided to not show any information about the data item if there is no info on what columns are relevant.
I was thinking to maybe do str(data_item.get("first_column_name")[:50] or something like that but it seemed a bit risky to me. what if the column is super huge or is bytes or whatnot?
89a50d5 to
5070ffd
Compare
anuunchin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧠
…resent (dlt-hub#2915) * improve DataValidationError output: use identifying columns if present * removing duplicate `schema: {schema_name}` from error message * refactor