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
With the supported catalogs increased, Gravitino will face a problem that current type system cannot cover all the scenarios, like unsigned types, UDTs. In the meantime, we need to support DDL, so we should cover all the types.
How should we improve?
So to handle this problem, we should:
Support UDTs, developers can define their own types based on our frameworks to support customized scenario.
Support type variations to mapping the types to the target system.
The issue discussed in #1761 is also something that needs to be considered for the universal type:
the types in Gravitino have the same name as the types in the catalog, but they have different semantics.
What would you like to be improved?
With the supported catalogs increased, Gravitino will face a problem that current type system cannot cover all the scenarios, like unsigned types, UDTs. In the meantime, we need to support DDL, so we should cover all the types.
How should we improve?
So to handle this problem, we should:
We can refer to Substrait's type system (https://substrait.io/types/type_system/) to achieve our own.
CC @mchades @yuqi1129 @zhoukangcn
The text was updated successfully, but these errors were encountered: