Apply the version correction before testing string-coordinate storage
Do not generalize an old-version failure to current support. Admit string coordinates using a roundtrip on the actual installation.
A storage boundary after input typing
Input string-type checks and approval of actual storage and rereading are separate. Test whether coordinates can be read from a small destination before deciding support. Repeating only the original error can discard a compatible path; checking str inputs alone cannot promise writer completion. An operator-completed test-write status table lets Truthound compare actual and required completion. [1, 2, 3]
The reporter corrected the version
Xarray #11267 initially reported a Zarr v3 string-coordinate type error. The reporter then corrected the report: an old version had been used, and switching to Xarray 2025.6.1 worked. The evidence includes both statements, without turning that installation experience into a release guarantee for every codec combination. [1]
Measure completion in a test destination
Write string coordinates to a separate test destination and record actual reread completion and original values. Keep failed paths out of operational storage while evaluating compatible formats or explicit encoding. Do not overwrite the source, and supply the actual writer result and reread strings. [1, 3]
A contract for two coordinates
The illustrative storage policy requires writing and rereading station coordinates DE210000 and DE210001. The required success flag is true, backed by preservation of both values. A completed, matching roundtrip passes; a failed write or incomplete reread gives false and fails. Do not infer completion from input types. [1, 3]
An API for the prepared result table
ColumnPairValidator in Truthound Python SDK 3.3.2 can compare the roundtrip-success flag produced by operator-run writers and readers with the required state. Keep original coordinates as its evidence. This does not discover codec support automatically or attribute the failure to a particular library, and it does not imply general string failure in current Xarray. [1, 2, 3]
Reread after choosing a compatible stack
Test a verified version combination and check the actual string-coordinate write and reread values. The reporter’s 2025.6.1 success does not guarantee every installation. Conversely, an existing successful regression test for the relevant stack weakens any inference of failure from the original report alone. [1, 3]
Application conditions
Provide actual writer results and reread coordinates from a test destination that does not overwrite the source.
Alternatives
Verify a supported stack, actually write and reread the string coordinates, and reconcile their original values.
Limitations
This check does not automatically discover codec support or guarantee every installation from the reporter’s success.
Evidence
- Event checked
- Subject checked
- Modified
