Require an explicit Doris auto-partition RPC status
Do not fill an absent wire status with default OK in an automatic-partition response. Check for an explicit response and then visible keys in the new partition as separate completion boundaries.
Explicit status is the first boundary
An absent status field must not be promoted to success. Confirm delivery of rows requiring a new partition separately. Truthound Core can inspect a prepared status-presence record before downstream completion accepts a default OK. [1, 2, 3]
An unsent NOT_MASTER report
Doris issue #70258 is a source-review report: a non-master FE builds NOT_MASTER without attaching it to the response, allowing a BE default value to appear OK. The failover outcome is not an executed reproduction. Follow-up analysis also qualifies filtering tolerance and separates replacePartition effects. [1]
Join response and delivered rows
Join RPC wire-field presence, interpreted status, FE role changes, new partition inventory, and input-key outcomes. An unreachable FE is a transport error, not this missing-field path. Retain load counters and error records when filtering is allowed. [1, 3]
A default zero is not wire evidence
The illustrative response contract requires an explicitly transmitted status. status_present=true passes that prerequisite; false fails even if a Thrift default displays numeric 0 or OK. A passing presence flag still leaves actual OK and partition creation to subsequent checks. [1, 3]
Preserve absence as null
NotNullValidator in Truthound Core Python SDK 3.3.2 can reject a genuinely missing field in an operator-prepared response table. Preserve wire absence as null instead of filling a default. The SDK does not repair RPC serialization, redirect a load, or establish complete row delivery. [1, 2, 3]
Retry against the same input
Classify missing status as an error and verify the supported retry path against the same input keys. A positive filter tolerance alone does not imply success; the actual filtered fraction must fit the configured threshold. [1, 3]
Use two acceptance stages
Use explicit response evidence for the first approval boundary and visible keys for the next. This keeps a malformed acknowledgment from becoming a completed-partition claim while avoiding an unsupported claim that every missing status caused data loss. [1, 3]
Application conditions
Prepare RPC records retaining actual wire-status absence as null.
Alternatives
Classify missing status as an error and verify a supported retry for the same keys.
Limitations
An explicit status does not suffice to establish partition creation or all-row visibility.
Evidence
- Event checked
- Subject checked
- Modified
