Kerchunk user code currently passes around an obscure multiply-nested "reference dict" object. This is hard to read, interrogate, validate, or reason about.
SuggestionInstead create a new VirtualZarrStore
dataclass, which contains all the same information that is currently stored in the reference dict but in a more structured manner. This would then be the principle object that gets passed around between user calls to kerchunk API.
.to_json
, to_parquet
, .to_dict
or similar.)VirtualZarrStore
objects.to_json
is analogous to the ZOM's .serialize
), which then would be solidified as the recommended abstract representation once ZEP006 is acceptedVirtualZarrStore
should be basically a json schema (see #373)cisaacsterncisaacstern, sharkinsspatial, NikosAlexandris and abarciauskas-bgse
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4