Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
There are a couple of inter-related issues:
- Cases where a system might send the schema without the dictionaries, and the user wishes to reason about the schema and its types without knowing the dictionary values
- Dictionaries that are changing, e.g. using delta dictionary messages
arrow::DictionaryType has no "linkage" to any external object. I propose adding a "LinkedDictionaryType" or something similar (purely a C++ construct), which functionally would be a subclass of DictionaryType, which would allow a type to be created which will obtain its dictionary later through some kind of "Dictionary provider" interface. There is something similar in Java already. This would allow a dictionary to evolve via delta dictionaries, or for a dictionary to be retrieved later e.g. through an RPC or IPC layer
Attachments
Issue Links
- blocks
-
ARROW-1278 Integration tests for Fixed Size List type
-
- Resolved
-
- causes
-
ARROW-5361 [R] Follow DictionaryType/DictionaryArray changes from ARROW-3144
-
- Resolved
-
- is depended upon by
-
ARROW-5279 [C++] Support reading delta dictionaries in IPC streams
-
- Closed
-
-
ARROW-3325 [Python] Support reading Parquet binary/string columns directly as DictionaryArray
-
- Resolved
-
-
ARROW-5336 [C++] Implement arrow::Concatenate for dictionary-encoded arrays with unequal dictionaries
-
- Resolved
-
- is related to
-
ARROW-5338 [Format][Integration] Define how to test for delta dictionary support in the JSON integration test data format
-
- Open
-
- links to