Hi Dmitri My take on "Polaris interoperability" is between query engines: any query engine supporting the Iceberg REST API can use Polaris. The purpose is to have an unique Polaris across query engines, in order to centralize security. Today, in organizations, we often have several query engines (for example, Flink for streaming engines, Spark for transformation, Dremio for analytics, etc). So, it's important to have an "interoperable" catalog usable by any engine. Another take on "interoperability" is also between catalogs. As Polaris supports external catalogs, we can see a kind of interoperability between Polaris and other catalogs.
It's my view, others might have another one (please share here :)). Maybe it's worth adding a section in the documentation to define "Polaris interoperability". Regards JB On Wed, Oct 23, 2024 at 11:23 PM Dmitri Bourlatchkov <dmitri.bourlatch...@dremio.com.invalid> wrote: > > Hi All, > > The Polaris GH repo has this statement: "Apache Polaris, the interoperable, > open source catalog for Apache Iceberg". > > How is this "interoperability" defined? Do we have any docs that talk about > that? > > If not, what is the general perception in this community about what is > considered interoperable and what is not? > > Thanks, > Dmitri.
