Hi Mayur, Did you try Hive Metastore local mode? In that case, you have your postgres as the catalog DB, you can use all HMS's functionalities. However, you still need to handle Table access permission(your 3rd point) by yourself.
Best, Yufei `This is not a contribution` On Tue, May 11, 2021 at 11:46 AM Mayur Srivastava < mayur.srivast...@twosigma.com> wrote: > Hi, > > I’m looking to use/implement a PostgreSQL based Iceberg catalog. I’m > wondering if one already exists and also have a few questions. I would > really appreciate any help I can get with the questions. > > 1. Does Iceberg have a catalog that is compatible with PostgreSQL > (or any storage backend that is compatible with PostgreSQL)? > > a. If there are similar implementations, could someone share their > experience with the database schema used for the catalog? E.g. does a > namespace map to a database in the catalog backend? > > b. Is there an existing abstract base class that I can use to > implement the catalog that talks to PostgreSQL? > > 2. Mapping catalog namespace with S3 bucket: does someone have a > recommendation of managing catalog namespace along with AWS S3 (or GCS) > buckets? For example, when a top level namespace is created in the catalog, > do users map it to a bucket or a sub-directory structure on S3? (this may > be useful for setting the similar access control for both catalog namespace > and the S3 bucket.) > > 3. Table access permission management: since metadata is stored in > two separate systems (table metadata in S3 and namespace/table location in > catalog), how are table access permissions kept in sync in these storage > systems? E.g. if a catalog is used with GCS, how are the > namespace/bucket/table access permissions kept in sync? > > 4. Undeleting or recovering a dropped table: does the catalog > support undelete operation? If the underlying S3 data is not purged, can > the catalog be used to recover the dropped table? > > > > Thanks, > > Mayur > > >
