Ah, I saw the generic table in the last point but I missed directory :) FYI, I'm working on a branch. You can see where I'm here: https://github.com/jbonofre/polaris/tree/volume (I plan to open the PR by the end of this week). I already included documentation to help the discussion: https://github.com/jbonofre/polaris/blob/volume/site/content/in-dev/unreleased/volumes.md
Regards JB On Tue, Mar 31, 2026 at 6:44 AM Yufei Gu <[email protected]> wrote: > +1, Volume is the alias of the "directory tables". > > Yufei > > > On Mon, Mar 30, 2026 at 9:42 PM Jean-Baptiste Onofré <[email protected]> > wrote: > > > Hi Yufei > > > > It looks like great topics! > > > > I would add "Volume" as I have a PR on the way. > > > > 1. Regarding delegation service, we can include a pass on > > https://github.com/apache/polaris/pull/3990 and update it. > > 3. Good idea > > 5. I would like to add the topic about Polaris Console heading to first > > release > > > > NB: I will be late to join the Community Sprint as I should touch down > > around 1:30pm at SFO. > > > > Regards > > JB > > > > > > On Tue, Mar 31, 2026 at 6:27 AM Yufei Gu <[email protected]> wrote: > > > > > Hi folks, > > > > > > Excited about the upcoming Polaris community sprint! > > > https://luma.com/q8w8v7as > > > > > > Here are a few initial topics we can discuss in the sprint: > > > > > > 1. Delegation service, how Polaris can support TMS and other async > > tasks > > > such as drop by purge and server side scanning > > > 2. Federation architecture, especially authZ models and credential > > > vending boundaries > > > 3. Storage and credential configuration model, how we can simplify > and > > > unify it > > > 4. Eventing and metrics, what should live in Polaris vs upstream > > > 5. Developer ergonomics, setup, CLI, docs, and first time user > > > experience > > > 6. Catalog extensibility, plugin model, SPI boundaries, and real use > > > cases > > > 7. Performance and scalability, pagination, authZ filtering, and > large > > > catalog behavior > > > 8. Generic table features, directory tables and Parquet tables, > > > credential vending, and how we can broaden engine support > > > > > > Feel free to add anything else you’d like to discuss. The more input we > > get > > > upfront, the more productive the sprint will be. > > > > > > Looking forward to it! > > > > > > Yufei > > > > > >
