Skip to content

Conversation

@djudjuu
Copy link
Contributor

@djudjuu djudjuu commented Jul 22, 2025

@djudjuu djudjuu linked an issue Jul 22, 2025 that may be closed by this pull request
@netlify
Copy link

netlify bot commented Jul 22, 2025

Deploy Preview for dlt-hub-docs canceled.

Name Link
🔨 Latest commit 74bdd99
🔍 Latest deploy log https://app.netlify.com/projects/dlt-hub-docs/deploys/689065f6e96e3b000857c160

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:
Copy link
Contributor Author

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?

@djudjuu djudjuu changed the title improve DataValidationError output: use identifying columns if present QoL: improve DataValidationError output: use identifying columns if present Jul 22, 2025
@djudjuu djudjuu force-pushed the QoL/1772/show-offending-item-in-logs-when-schema_contract-is-set-to-freeze branch from 89a50d5 to 5070ffd Compare July 22, 2025 12:30
@djudjuu djudjuu self-assigned this Aug 1, 2025
@djudjuu djudjuu requested a review from anuunchin August 1, 2025 09:27
@djudjuu djudjuu requested a review from anuunchin August 4, 2025 07:49
Copy link
Contributor

@anuunchin anuunchin left a comment

Choose a reason for hiding this comment

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

🧠

@djudjuu djudjuu merged commit 9348319 into devel Aug 4, 2025
59 of 61 checks passed
AyushPatel101 pushed a commit to AyushPatel101/dlt that referenced this pull request Aug 8, 2025
…resent (dlt-hub#2915)

* improve DataValidationError output:  use identifying columns if present

* removing duplicate `schema: {schema_name}`  from error message

* refactor
@rudolfix rudolfix deleted the QoL/1772/show-offending-item-in-logs-when-schema_contract-is-set-to-freeze branch September 14, 2025 11:37
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.

Show offending item in logs when schema_contract is set to "freeze"

3 participants