You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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?
Beta Was this translation helpful? Give feedback.
All reactions