Styxis
Company
Knowledge

Use full physical paths when protecting Delta clustering fields

Do not treat matching leaf names in different structs as the same clustering column. Resolve the deletion target's full physical path and field ID to investigate a false rejection while preserving the column that actually needs protection.

Leaf names are not field identities

Clustering protection needs the full physical path or stable field ID, not a shared leaf string. Truthound Core can compare a prepared target classification with an independently identified clustering field. [1, 2, 3]

Rejecting t.x as though it were s.x

Delta Kernel issue #7976 reports master and 4.3.1 rejecting a drop of unclustered t.x when clustering s.x has the same physical leaf col-x. The parent path is lost in the protection set. It concerns a false rejection, not a report that the clustering column was actually dropped. [1]

Keep complete path components

Record display path, physical path components, field ID, clustering membership, and the drop target. Check that t.x is not classified as s.x. Do not resolve this by assuming all equal leaf names have equal column identity. [1, 3]

Shared col-x with distinct parents

Define clustering only on s.x and request a drop of t.x. Both leaves may be col-x, but their parents differ. Expected target_is_clustering=false. false passes; true fails the classification contract and calls for schema-plan review. [1, 3]

Comparison is not schema authorization

ColumnPairValidator in Truthound Core Python SDK 3.3.2 can compare the prepared non-null classification with false. The operator independently resolves full paths and IDs. The SDK does not authorize Kernel schema updates or alter clustering configuration. [1, 2, 3]

Retain actual clustering protection

Review a supported correction path and retain a control proving that dropping actual clustering s.x is still rejected. Allowing the unrelated drop must not accidentally remove the protection being tested. [1, 3]

Identify which x the error means

An error mentioning x does not show which x was protected. Preserve complete identities in the approval artifact so a leaf-name collision can be diagnosed without changing the table’s intended clustering policy. [1, 3]

Application conditions

Identify clustering-protected fields by full physical path and field ID.

Alternatives

Verify a supported correction preserving rejection of actual s.x drops.

Limitations

  • A shared leaf name means neither the same field nor an approved scope change.

Evidence

Event checked
Subject checked
Modified