Same comment as in the other thread regarding location and generic table: how are clients supposed to interact with this format? Could we have a detailed discussion about the protocol between the catalog and the query engine?
Laurent On Fri, Jun 13, 2025, 17:01 Vinoth Chandar <vin...@apache.org> wrote: > +1 > > I am on the Hudi PMC. This will nicely augment our HMS++ metastore and > Apache Gravitino support. Bring a lot of benefits to both Hudi and Polaris > communities. > > On 2025/06/13 22:54:43 yun zou wrote: > > Hi Rahil, > > > > Thanks a lot for working on this! This is definitely one valuable feature > > improvement for > > the Spark Client support, I am really looking forward to that! > > > > The overall approach looks good to me! > > > > Best Regards, > > Yun > > > > On Fri, Jun 13, 2025 at 3:47 PM Yufei Gu <flyrain...@gmail.com> wrote: > > > > > Thanks for the proposal. +1 on adding Hudi support. Since Hudi doesn’t > > > currently have an IRC (Iceberg REST Catalog)-like specification, the > > > proposed approach looks reasonable. > > > > > > Yufei > > > > > > > > > On Fri, Jun 13, 2025 at 8:41 AM Rahil C <rchert...@gmail.com> wrote: > > > > > > > Hi all, > > > > > > > > I would like to start a discussion about adding support for Apache > Hudi > > > > tables within Apache Polaris. > > > > > > > > I was able to look into the recent integration that was done for > adding > > > > Delta as a Generic Table within Polaris > > > > <https://polaris.apache.org/in-dev/unreleased/polaris-spark-client/ > >, > > > and > > > > believe that we can do an approach for Hudi that adds changes to the > > > > Polaris Spark Plugin that follows a similar pattern. > > > > > > > > I have put out an initial "draft" pr here, which more concretely > > > > demonstrates this integration: > > > https://github.com/apache/polaris/pull/1862 > > > > > > > > Would appreciate thoughts/guidance from the community on how we can > > > support > > > > this initiative. > > > > > > > > Regards, > > > > Rahil Chertara > > > > > > > > > >
