UI support for Apache Polaris

[MonkeyCanCode]

As of today, both Nessie and Unity Catalog offer user interfaces (UIs) for both open source and enterprise editions. In contrast, Apache Polaris currently only supports a UI through the Snowflake service, with no UI available for the open source version. Are there any plans to address this gap?

Regarding Apache Amoro, they are awaiting the initial release of Apache Polaris before considering integration support, particularly if we do not develop our own UI (see: apache/amoro#3089).

If we decide to develop our own UI to match the feels and looks of the enterprise edition, are there any preferred programming languages or frameworks that we should use before submitting a pull request?

[lamb-russell]

i am in the process of writing my own Electron GUI that uses the CLI as the backend. Please feel free to use and/or contribute. https://github.com/lamb-russell/polaris-electron-app

[RussellSpitzer]

I'm open to including a UI in the project, so any proposals would be welcome

[lamb-russell]

I can add a few more features to the UI I'm building. It currently has implemented the basic features of the CLi: eg, list, create, delete, grant, revoke. So far catalog, principal, and principal role are implemented. if you think it could be a good UI for Polaris i can either link to the repo in the docs or even add it to the code base.

[jbonofre]

I think it makes sense to have an UI in the project.
I would go with React + Ant design as first layer, pretty aligned with what's coming in Polaris.
I can draft something around that (I did several admin consoles using this).

A first step would be to manage the entities (tables and views) via the UI (creating/updating/removing entities), the RBAC model (managing principals and roles) and also preparing additional management layer (like the maintenance notification layer we are discussing).

[lamb-russell]

JB good idea to use Ant for design. So far I got managing several entities (catalog, principal, principal role, catalog role) into the react gui.

…

On Tue, Oct 22, 2024 at 5:50 AM JB Onofré ***@***.***> wrote: I think it makes sense to have an UI in the project. I would go with React + Ant design as first layer, pretty aligned with what's coming in Polaris. I can draft something around that (I did several admin consoles using this). A first step would be to manage the entities (tables and views) via the UI (creating/updating/removing entities), and also preparing additional management layer (like the maintenance notification layer we are discussing). — Reply to this email directly, view it on GitHub <#306 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATAFNLH7Q3XWG6DJRQTECATZ4YNU7AVCNFSM6AAAAABOKUYVMKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMBRGUYTAOA> . You are receiving this because you commented.Message ID: ***@***.***>