Styxis
Company
Knowledge

Keep Hudi record-index scope unchanged during a size rebuild

Check that a size-oriented index rebuild preserved its partitioned or global scope. Reconcile the prior definition with effective configuration rather than inferring identity from a shared metadata name.

Size changes preserve index identity

A size rebuild must preserve index scope unless changing scope was explicitly approved. Truthound Core can compare prepared partitioned/global identity fields before the rebuild result becomes operational evidence. [1, 2, 3]

A shared-name rebuild report

Hudi issue #20343 reports HoodieIndexer identifying an index only by the shared record_index partition name and rebuilding a partitioned record-level index with global settings. The supplied user properties are overwritten later, so simply resending them is not the reported workaround. [1]

Retain authoritative and effective config

Retain table configuration and the authoritative index definition before rebuilding. Compare effective Indexer properties and the resulting layout afterward. A shared metadata partition name cannot establish the same key scope. [1, 3]

The partitioned-scope fixture

Define the illustrative request as a size adjustment with no approved scope change. Existing scope partitioned therefore expects partitioned after rebuilding. partitioned passes; global fails even though both use record_index. This is an identity condition, not a file-size measurement. [1, 3]

Check lookups after label equality

ColumnPairValidator in Truthound Core Python SDK 3.3.2 compares prepared non-null scope columns with ==. The operator must choose the authoritative definition and capture effective configuration. The SDK does not change HoodieIndexer property precedence. [1, 2, 3]

Review a supported rebuild

Review a verified supported rebuild procedure or correction, then check same-partition key lookups and file-group sizing. Follow-up comments discuss work and review readiness without providing a verified deployment result. [1, 3]

Separate identity from physical correctness

Scope equality leaves physical layout and lookup correctness unproven. Keeping those later checks separate makes it possible to reject a changed index identity early without claiming that a matching label certifies every lookup. [1, 3]

Application conditions

Prepare authoritative pre-rebuild scope and actual effective properties/layout.

Alternatives

Check partition lookups and file-group size after a supported rebuild path.

Limitations

  • Equal scope labels do not prove every physical layout or key lookup.

Evidence

Event checked
Subject checked
Modified