Follow the corrected Unity Catalog URI contract for literal percent paths
Check percent-bearing locations by distinguishing URI text from the storage key it represents. Follow the correction toward UC's input and output boundary instead of repeating the withdrawn Delta fix as a remedy.
A discrepancy does not justify a client patch
A location mismatch does not automatically justify changing Delta URI conversion. Check the agreed URI exchange contract on both sides. Truthound Core can compare the finally resolved object key with an independent literal storage name. [1, 2, 3]
The author’s corrected diagnosis
The author of Delta issue #7999 later corrected the diagnosis to Unity Catalog. Delta sending and reading URI representations is described as reasonable; the UC change in #2101 decodes incoming locations and returns URI-encoded locations. The author says both repros pass on Delta 4.3.1 without a Delta change. [1]
Do not require raw text equality
Separate the original Delta diagnosis from that correction. Preserve literal object name, required URI form, UC received and returned forms, and resolved key. Do not enforce raw text equality across URI and storage representations. [1, 3]
Literal percent versus URI escape
Define the actual folder as literal team%20reports. Its URI form may correctly contain team%2520reports. After one contract-defined interpretation, final key team%20reports passes; team reports fails because it names a different folder. The reference is the resolved object key, not identical URI text. [1, 3]
The initial proposal was withdrawn
ColumnPairValidator in Truthound Core Python SDK 3.3.2 compares prepared non-null resolved-key tokens with the independent key. The operator implements the agreed parsing contract. The SDK does not modify UC or URI parsers, and the initial proposed Delta fix was withdrawn. [1, 2, 3]
Check the deployed exchange contract
Check the actual UC and Delta versions’ exchange contract with literal-percent and space controls. The author’s two passing repros are a scoped follow-up report, not assurance that every version or path has been repaired. [1, 3]
The correction changes the action
Retaining the correction changes the operational decision: investigate the server/client boundary before patching the client. Repeated decoding can merge distinct objects, so the accepted interpretation must be explicit and singular. [1, 3]
Application conditions
Independently prepare the literal object key and the agreed single URI interpretation.
Alternatives
Verify percent and space controls under the actual UC/Delta contract.
Limitations
The initial Delta fix proposal was withdrawn; UC follow-up passes do not guarantee every version.
Evidence
- Event checked
- Subject checked
- Modified
