Truthound · All articles · 17/24
Evidence-led Truthound Core guidance on data contracts, check inputs and operational limits.
480 articles
After a Trino Iceberg type promotion, is an unfiltered SELECT enough?
Schema-transition readiness requires both the unfiltered read and the filter paths actually used by consumers.
Trino filters after a Hive decimal change: inspect Parquet storage type and scale
Interpreting old integer-file statistics through only the current schema can prune matching rows.
Rows visible in Trino after Hive ACID TRUNCATE: validate the transaction state
The consumer's approved post-TRUNCATE view matters more than whether old physical files still exist.
Two active SCD rows in Trino? Inspect non-key statistics in the delete file
Pruning an equality-delete file using payload-field statistics can leave an old version active beside its replacement.
Trino decimal-bucket join omissions: compare parallel runs on one snapshot
When fixed inputs produce unstable results, inspect key-level task assignment and match presence rather than only value ranges.
Migrating Shopify tracking numbers when the singular field overrides the array
Adding the plural tracking field is insufficient if the old singular field remains in the request.
Shopify shipment webhooks: preserve transfer IDs and verify the reference scope
An explicit transfer ID reduces inferred joins, but reference existence and correct linkage still need separate checks.
Validating Shopify selling_plan_id without rejecting normal null values
The new webhook field carries the selling plan for subscription items. Requiring it on ordinary purchases rejects valid data.
Shopify return shipping tax: pending null is different from a finalized zero
Estimated and finalized tax have different calculation times. Reconciliation must preserve finalization state as well as amounts.
Shopify inventory reactivation: omitted quantity is not an explicit zero
When reactivation defaults change, the operational assumption that activation resets stock must change with them.
Shopify FULFILLMENT_NOT_REQUIRED: distinguish unfulfilled from nothing left to fulfill
Mapping the new status to a generic unfulfilled queue can leave orders with no remaining work in the dispatch backlog.
Shopify Metaobject values updates differ from patches that preserve omitted fields
Convenient serialization through values comes with clearing semantics. Record the intent to retain fields as a separate contract.
Shopify market relationships: restart pagination when the version changes
Stable relationship IDs do not imply stable cursors during a rebuild. Separate collection generations before accepting the hierarchy.
Shopify cancellation handoff: separate job acceptance from jobResult evidence
Acceptance of an asynchronous cancellation request is not evidence for a completion notice. Define where cancellation-specific results must be checked.
Updating multiple Shopify barcodes: an apparent addition can replace the entire set
Sending only a new value in barcodes can remove an existing identifier. Check the complete set and first-entry compatibility separately.
RisingWave DELETE after an upsert: inspect prior state before cancelling operations
Deleting a new insertion and deleting an overwrite of an existing row are different state transitions.
RisingWave materialized-view NULL updates: compare missingness states explicitly
Changing a value to NULL is a state transition to preserve, not the absence of an update.
RisingWave CDC name collisions: verify live routing separately from backfill
A topic name normalized from special characters may not uniquely identify its original source table.
Pulsar replay after partial batch ACK: check duplicate business effects
An ACK completion signal and one-time business effects after recovery are separate contracts.
Polars zero-column round trips: preserve height 3 as independent state
An empty column array does not imply zero rows. Check explicit height across an extension interface.
