Hi EJ, JB, I left some comments on EJ's doc. I actually have a lot of comments on the REST API design, I only posted some of them to start a discussion without overloading the doc.
Overall, I believe EJ's proposal should also allow permission assignments on tags that JB proposed (eventually). We just need to clearly define the persistence expectations for looking up related tags on the read path. We should probably specify whether and how tags are exposed to authorizers (OPA, Ranger). I imagine people will want to use them in external policy engines the moment the feature is available. On the persistence side, I believe it would be nice to define actual java interfaces (perhaps in pseudo code) to allow easier review from the NoSQL persistence perspective (also commented in the doc). Cheers, Dmitri. On Thu, Jul 30, 2026 at 12:39 AM Jean-Baptiste Onofré <[email protected]> wrote: > Hi EJ > > Thanks for starting this discussion. > > For the record, here's my initial proposal about tagging: > https://lists.apache.org/thread/nmqmmjfmocfllb71fcmyp9syc9gyn820 > > At that time, only Dmitri replied :) > So, I would be happy to work with you on this, as I still have the PoC > I created for my initial proposal. > > I will try to join the scheduled meeting (no guarantee). > > Regards > JB > > On Fri, Jul 17, 2026 at 6:53 AM EJ Wang <[email protected]> > wrote: > > > > Hi folks, > > > > I have prepared a Google Doc > > < > https://docs.google.com/document/d/1rIJGzcsmGhfrBiRXPac51hr-jeJuuKQQBYjgBdOb9-k/edit?usp=sharing > > > > for the Polaris tag spec proposal. > > > > The goal is simple: add a native tag model to Polaris so users can > classify > > catalog objects, read those classifications back, and find objects by > tag. > > > > The proposal covers: > > * tag definitions as catalog-scoped Polaris entities > > * tag assignments on catalogs, namespaces, table-like objects, and > columns > > * allowed values on tag definitions > > * direct and inherited tag reads > > * direct by-tag lookup > > * the durable model behind the API > > * how this compares with the existing Polaris Policy API (tag design > > referenced policy heavily, given their pattern similarity) > > > > Please take a look and leave comments in the doc. Let me know WDYT! > > > > I would also like to discuss this in the July 23 community sync. A > separate > > dedicated review meeting will be scheduled separately, likely within the > > next two weeks. > > > > Thanks, > > -ej >
