You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The schema.fbs and corresponding generated code has no concept of a Dictionary datatype.
However, we declare a DataType::Dictionary.
Additional context
As a user, I would like to be able to not have to change my DataType whenever I want to change an arrays' encoding. In the context of DataFusion, that uses DataType to declare the schema of the logical plan, this forbids optimizations at the physical level that e.g. would convert an array to a dictionary-encoded array, which is useful in any group-by or hashing operation.
The text was updated successfully, but these errors were encountered:
table DictionaryEncoding is part of the definition of table Field, theoretically we could move the dictionary-ness onto Field. However, this would complicate downcasting, and given Field is part of Schema regardless, this wouldn't change the fact that dictionary-ness is an inherent part of an array's schema.
Describe the bug
The schema.fbs and corresponding generated code has no concept of a
Dictionary
datatype.However, we declare a
DataType::Dictionary
.Additional context
As a user, I would like to be able to not have to change my
DataType
whenever I want to change an arrays' encoding. In the context of DataFusion, that usesDataType
to declare the schema of the logical plan, this forbids optimizations at the physical level that e.g. would convert an array to a dictionary-encoded array, which is useful in any group-by or hashing operation.The text was updated successfully, but these errors were encountered: