Test catalog connection
POST/metalakes/:metalake/catalogs/testConnection
Test catalog connection
Request
Path Parameters
The name of the metalake
- application/json
 
Body
The name of the catalog
Possible values: [relational, fileset, messaging, model]
The type of the catalog
Possible values: [hive, lakehouse-iceberg, lakehouse-paimon, lakehouse-hudi, jdbc-mysql, jdbc-postgresql, jdbc-doris, jdbc-oceanbase, hadoop, kafka]
The provider of the catalog
A comment for the catalog
properties
object
nullable
A map of properties for the catalog
Responses
- 200
 - 400
 - 5xx
 
Test connection completed
- application/vnd.gravitino.v1+json
 
- Schema
 - Example (from schema)
 - TestConnectionSuccess
 - TestConnectionFailed
 - CatalogAlreadyExists
 - MetalakeNotFound
 
Schema
Status code of the response
Internal type definition of the exception
The message of the exception
{
  "code": 0,
  "type": "string",
  "message": "string",
  "stack": [
    "string"
  ]
}
{
  "code": 0
}
{
  "code": 1007,
  "type": "ConnectionFailedException",
  "message": "Failed to run getAllDatabases in Hive Metastore: Failed to connect to Hive Metastore",
  "stack": [
    "org.apache.gravitino.exceptions.ConnectionFailedException: Failed to run getAllDatabases in Hive Metastore: Failed to connect to Hive Metastore",
    "..."
  ]
}
{
  "code": 1004,
  "type": "CatalogAlreadyExistsException",
  "message": "Failed to operate catalog(s) [my_catalog] operation [CREATE], reason [CatalogAlreadyExistsException]",
  "stack": [
    "org.apache.gravitino.exceptions.CatalogAlreadyExistsException: Catalog my_catalog already exists",
    "..."
  ]
}
{
  "code": 1003,
  "type": "NoSuchMetalakeException",
  "message": "Failed to operate metalake(s) [test] operation [LOAD], reason [NoSuchMetalakeException]",
  "stack": [
    "org.apache.gravitino.exceptions.NoSuchMetalakeException: Metalake test does not exist",
    "..."
  ]
}
Indicates a bad request error. It could be caused by an unexpected request body format or other forms of request validation failure, such as invalid json. Usually serves application/json content, although in some cases simple text/plain content might be returned by the server's middleware.
- application/vnd.gravitino.v1+json
 
- Schema
 - Example (from schema)
 - Example
 
Schema
Possible values: >= 1000 and <= 1100
HTTP response code
Internal type definition of the error
A human-readable message
{
  "code": 1002,
  "type": "string",
  "message": "string",
  "stack": [
    "string"
  ]
}
{
  "code": 1003,
  "type": "BadRequestException",
  "message": "Malformed request"
}
A server-side problem that might not be addressable from the client side. Used for server 5xx errors without more specific documentation in individual routes.
- application/vnd.gravitino.v1+json
 
- Schema
 - Example (from schema)
 - Example
 
Schema
Possible values: >= 1000 and <= 1100
HTTP response code
Internal type definition of the error
A human-readable message
{
  "code": 1002,
  "type": "string",
  "message": "string",
  "stack": [
    "string"
  ]
}
{
  "code": 1002,
  "type": "RuntimeException",
  "message": "Internal Server Error",
  "stack": [
    "java.lang.RuntimeException: Internal Server Error"
  ]
}