GitHub user liunaijie added a comment to the discussion: Support Internal Catalog
> To create a catalog, the gravitino needs to be bound to hms or jdbc. We can > call it an external catalog. It is hoped that creating a catalog does not > require specifying an external metastore; it is referred to as an internal > catalog. > > When creating a catalog in UnityCatalog, there is no need to specify a > metastore. Table metadata stored in unitycatalog: > https://github.com/unitycatalog/unitycatalog/blob/b141f19665c0c88ed6b72a04149881690ac29dcd/server/src/main/java/io/unitycatalog/server/persist/TableRepository.java#L108 Thanks for your reply, but it still hasn't cleared up my confusion. For the external catalog, every entity—such as a `Table` or `Topic`—has a corresponding counterpart in other systems (e.g., a Hive table or Kafka topic). Gravitino serves as a unified system to manage all these entities collectively. So, regarding the internal catalog: what do a `Entity (Table)` represent? > Technically, an HMS is required. If the customer requests a cloud-native > solution, they may question why an HMS is still needed (believing that only > Hadoop would require an HMS). It is hoped to find an alternative solution to > HMS. It is believed that more people have such demands. what's the relationship between `cloud-native` and `metadata`? As someone who's just starting to learn about these concepts, I'd really appreciate it if you could explain this to me in a way that's easy for a novice to grasp—thank you! GitHub link: https://github.com/apache/gravitino/discussions/7652#discussioncomment-13730418 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
