+1 to this. I would also recommend thinking about this from an interface POV to have BaseMetastoreCatalog (from Apache Iceberg) as a way to integrate, with a defined connection object that can feed the connection to BQ or Glue (perhaps a standard key-value prep) and the dependencies can be added accordingly.
Thanks, Prashant Singh On Tue, Mar 17, 2026 at 12:08 PM Dmitri Bourlatchkov <[email protected]> wrote: > Hi Joy, > > I suppose Polaris will be the REST API + AuthZ layer on top of > BigQueryMetastoreCatalog, right? How do you envision this? > > In general, I think it's going to be a useful contribution. > > From my POV, the only technical issue we need to be careful about is > proper modularization to control dependency scope growth. I imagine some > downstream projects may want to opt in/out of BigQueryMetastoreCatalog and > its transitive dependencies at their own discretion. > > Cheers, > Dmitri. > > On 2026/03/17 18:19:34 Joy wrote: > > Hi, > > > > I'm Joy. We use BigQueryMetastoreCatalog for Iceberg on GCP and want to > use > > Polaris as a catalog gateway. I see federation currently supports REST > and > > HMS. > > > > Would there be interest in supporting other native Iceberg catalogs like > > BQMS or Glue? I've been working on a prototype for BQMS following the HMS > > pattern and would be happy to contribute it if I'm successful. > > > > Regards, > > Joy > > >
