search

datastrato / gravitino

World's most powerful data catalog service with providing a high-performance, geo-distributed and federated metadata lake.
https://datastrato.ai/docs/
Apache License 2.0
347 stars 150 forks source link

[Improvement] Gravitinoi UI can create new metalakes but not effectively use them in playground #3246

Open justinmclean opened 2 weeks ago

justinmclean commented 2 weeks ago

What would you like to be improved?

The Gravitino playground is configured to use simple names but the UI enables you to create new metalakes.

How should we improve?

Stop UI from being able to create new metalakes when using simple names?

shaofengshi commented 1 week ago

User still has the capability to create multiple metalakes. The only change is at the client (trino, spark) side, where they need to specify the metalake name in client configuration.

justinmclean commented 1 week ago

The issue is that you can only use one metalake and can't query between them - this can be confusing for the user.

shaofengshi commented 1 week ago

The issue is that you can only use one metalake and can't query between them - this can be confusing for the user.

Hi Justin, cross-metalake query should be very low-freqency: usually they are in the same metalake. But we still keep the possibility: for that case, user can set certain property in the client(Trino) side, after that they can use the full four-section name to do cross-metalake query. @diqiu50 Yu Hui can you confirm this?

justinmclean commented 1 week ago

If it is only low frequency then we need to change the UI. Currently, it's the first thing a user will see when they start up the Gravitino UI.

image

Note the most prominent call to action is the "Create Metalake" button.

justinmclean commented 1 week ago

There is also no need for the filters on metalakes or the pagination.

diqiu50 commented 1 week ago

I think he ui is difference with Trino connector. Users can create a metalake on ui. And users can using one or more metalake in Trino

diqiu50 commented 1 week ago
<!DOCTYPE html> gravitino.simplify-catalog-names boolean true The gravitino.simplify-catalog-names setting omits the metalake prefix from catalog names when set to true. NO 0.5.0

We can set gravitino.simplify-catalog-names = false to enable multiple metalakes support in Trino connector

justinmclean commented 1 week ago

How do you do that with the playground? By default, it is true, and thus the Gravitino UI can be confusing to a first-time user. In the playground, you can change the config, but no Trino admin tools are installed.

diqiu50 commented 1 week ago

This requires the Trino admin to modify the Trino connector configuration. Of course, you can also refer to the documentation. configuring-the-gravitino-connector

justinmclean commented 1 week ago

Yep, I understand that, but the playground doesn't include Trino admin. Put yourself in the shoes of a first-time user; how likely are they going to be able to do this?

diqiu50 commented 1 week ago

The purpose of this playground is to allow users to quickly experience it. It does not use advanced features. Using a simple catalog name makes it easier for ordinary users to get started. We recommend users to use it this way.

If you need to use the full catalog name, I can help you configure it

justinmclean commented 1 week ago

Sure, I get the purpose, but again, the UI in the playground makes it very easy for users to break things as the Gravitino UI playground assumes you can have multiple meta lakes, and the Tino playground doesn't.

shaofengshi commented 1 week ago

Sure, I get the purpose, but again, the UI in the playground makes it very easy for users to break things as the Gravitino UI playground assumes you can have multiple meta lakes, and the Tino playground doesn't.

Yeah, the UI has the room to improve. Today it is the first page for user to create metalake, actually in most of cases only 1 metadata is enough. We need to improve it in the future releases, e.g, not put it as the first page.