Styxis
Company
Knowledge

Check Doris VARIANT field presence when UTC Z parsing depends on aliases

After loading a Zulu timestamp, check presence and non-null state at the typed VARIANT path even if the row succeeded. Record the BE conversion context without treating later host state or a compaction observation as proof of cause.

Load counts do not preserve every field

Normal load counts do not prove that every required typed path survived. Truthound Core can compare prepared field-presence and missingness flags for matched Z and +00:00 timestamp controls. [1, 2, 3]

Downstream observation and master analysis

Doris issue #69326 reports downstream branch-3.1 field omission and analyzes a master alias dependency on Zulu. Master runtime reproduction and a compaction-specific cause are explicitly unestablished. Follow-up review says the actual storage conversion context, rather than the querying session, must be recorded. [1]

Inspect typed and complete output

Join raw timestamp, row ID, BE environment, typed-path presence, and non-null state. Compare Z with +00:00 through BE column conversion. Inspect both typed access and complete VARIANT output; successful row ingestion can coexist with field removal. [1, 3]

The required UTC field state

Declare required created_at=2015-01-01T03:47:41Z. Its prepared presence-and-non-null state should be true. true passes; false fails even when the containing row was loaded. This contract concerns a valid UTC input, not a policy to reject every nullable timestamp. [1, 3]

Prepare the flags externally

ColumnPairValidator in Truthound Core Python SDK 3.3.2 can compare non-null state flags with the independent required state. Extraction and conversion context come from the operator. The SDK does not install tzdata or recover discarded fields. [1, 2, 3]

Retain raw messages for recovery

Use an isolated Z versus +00:00 comparison and retain raw messages for targeted re-extraction. A parser correction affects future conversion; it cannot reconstruct values already discarded from storage. [1, 3]

Keep causal uncertainty visible

Keep the report’s causal uncertainty visible. Post-failure host files alone do not establish the failing process’s cache, and a mismatch after compaction does not prove compaction caused it. [1, 3]

Application conditions

Prepare BE conversion context and typed/full-VARIANT states for Z and +00:00.

Alternatives

After isolated controls, re-extract affected fields from raw messages.

Limitations

  • Distinguish downstream observation from master source hypotheses and compaction causality.

Evidence

Event checked
Subject checked
Modified