apache
[FEATURE] Support `testConnection` Without Catalog Name in Gravitino
Describe the feature
Description:
The testConnection method currently requires a catalog name, as it depends on Metalake, which enforces this. However, there are cases where we need to validate the connection using only provider and properties before creating a catalog. This limitation makes it difficult to test connections early in the workflow.
Motivation
- Enables connection testing before catalog creation.
- Simplifies workflows and enhances flexibility.
Describe the solution
Allow testConnection to work with just provider and properties, making the catalog name optional.
Additional context
No response
In actuality, the original intention behind the design of the testConnection interface was to validate the usability of the parameters in the createCatalog interface, plz see #4107.
Furthermore, to my knowledge, some users have already employed it as a preliminary validation interface for creating catalogs in the UI. If we were to make the catalog name optional, it would compromise the compatibility of this interface. Therefore, I do not recommend making such a modification.
I believe that utilizing a randomly generated catalog name when invoking the testConnection interface can still achieve the desired outcome you described, and there is no necessity for alterations to the interface.
