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
Currently, column is managed out of Gravitino, for example, column in a Hive table is gotten from HMS, column in an Iceberg table is gotten from Iceberg's metadata.
The current design choice avoids the duplication of maintaining column metadata both in Gravitino and underlying sources. But in the meantime, it brings some limitations like tagging on columns is hard to achieve in Gravitino.
So we should figure out a solution to handle this scenario: support some operations in Gravitino while keep consistency between two services for column.
Describe the feature
Currently, column is managed out of Gravitino, for example, column in a Hive table is gotten from HMS, column in an Iceberg table is gotten from Iceberg's metadata.
The current design choice avoids the duplication of maintaining column metadata both in Gravitino and underlying sources. But in the meantime, it brings some limitations like tagging on columns is hard to achieve in Gravitino.
So we should figure out a solution to handle this scenario: support some operations in Gravitino while keep consistency between two services for column.
Attach the design doc (https://docs.google.com/document/d/1X9kFeckDMrzqHo5fcOO55bnU0GIf2DM0KxheH4Nry54/edit?usp=sharing)
Tasks:
Motivation
No response
Describe the solution
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: