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
All databases can be viewed, even if the user specifies a JDBC URI with a schema name when creating a JDBC catalog like MySQL or PostgreSQL. For example, if the JDBC URL is jdbc:mysql://127.0.0.1:33540/db1, when we uses listSchema API to list schemes in the catalog, some other schemas can still be seen.
How should we improve?
So I suggest we shorten the last database name to in the creating process.
The text was updated successfully, but these errors were encountered:
In the Trino, the mysql connector only supports the jdbc url without a database. But, the postgressql connector only supports the url with a database.
What do you want to do about it? If the Graviton server does not report an error, do I need to make it compatible or report an error on the Trino connector
the postgressql connector only supports the url with a database
This shouldn't be an issue. In Gravitino, each PostgreSQL catalog is separated by database, so it seems be to okay for PG. I will only trim the database for MySQL, Doris, and leave PostgreSQL as is.
What would you like to be improved?
All databases can be viewed, even if the user specifies a JDBC URI with a schema name when creating a JDBC catalog like MySQL or PostgreSQL. For example, if the JDBC URL is
jdbc:mysql://127.0.0.1:33540/db1
, when we useslistSchema
API to list schemes in the catalog, some other schemas can still be seen.How should we improve?
So I suggest we shorten the last database name to in the creating process.
The text was updated successfully, but these errors were encountered: