mchades commented on issue #11215: URL: https://github.com/apache/gravitino/issues/11215#issuecomment-4540375558
This is a documented limitation rather than a bug. According to the Gravitino documentation, Iceberg catalog currently does not support Gravitino's table partition management operations, such as add/list/get/drop partitions: https://gravitino.apache.org/docs/1.2.0/manage-table-partition-using-gravitino#requirements-and-limitations This also aligns with Iceberg's native partition model. Iceberg uses `hidden partitioning`, where partition values are derived and tracked by Iceberg instead of being user-maintained Hive-style partition entries: https://iceberg.apache.org/docs/latest/partitioning/#icebergs-hidden-partitioning In Iceberg, partition-related operations are mainly modeled as partition spec evolution and metadata inspection, rather than add/list/drop concrete partition entries. For example, Iceberg exposes partition information through metadata tables such as the `partitions` table: https://iceberg.apache.org/docs/latest/spark-queries/#partitions Iceberg also does not encourage users to interact with tables through partitions because partitioning can evolve. There was a related Iceberg discussion where maintainers suggested using the partitions metadata table and noted that interacting through partitions is not encouraged because partitioning can change: https://github.com/apache/iceberg/pull/3459#issuecomment-962701637 Also, even Iceberg's `replace partitions` API is documented as "Not recommended" and exists mainly for Hive-compatible SQL; the recommended approach is explicit overwrite/data operations instead: https://github.com/apache/iceberg/blob/main/api/src/main/java/org/apache/iceberg/Table.java So I think the current behavior should not be treated as a Gravitino bug. Supporting Gravitino's Hive-style partition management APIs for Iceberg would require a separate feature/design discussion, and it may not align well with Iceberg's recommended partition model. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
