TimothyDing opened a new pull request, #10364:
URL: https://github.com/apache/gravitino/pull/10364

   ### What changes were proposed in this pull request?
   
   Add cloud-based integration tests for the Hologres JDBC catalog. Since 
Hologres is a managed cloud service on Alibaba Cloud, the tests connect to a 
real Hologres instance and are controlled by environment variables.
   
   New files:
   - `CatalogHologresIT.java`: Integration test class extending `BaseIT`, 
covering schema CRUD, table CRUD, type conversion (13 types), ALTER/DROP table, 
distribution key, table properties, primary key index, column default values, 
and schema comments.
   - `HologresService.java`: JDBC helper class for direct verification against 
the Hologres instance.
   - `README.md`: Documentation with environment variable configuration and 
test execution instructions.
   
   Modified files:
   - `CatalogManager.java`: Add `jdbc-hologres` to `CONTRIB_CATALOGS_TYPES` to 
ensure correct catalog path resolution in test environment.
   
   ### Why are the changes needed?
   
   The Hologres JDBC catalog only has unit tests for SQL generation and type 
conversion. It lacks end-to-end integration tests that verify the complete 
Gravitino workflow with a real Hologres instance. This PR fills that gap by 
following the cloud-service IT pattern used by 
`GravitinoVirtualFileSystemOSSIT`.
   
   Fix: https://github.com/apache/gravitino/issues/10362
   
   ### Does this PR introduce _any_ user-facing change?
   
   No.
   
   ### How was this patch tested?
   
   - Compilation verified via `./gradlew 
:catalogs-contrib:catalog-jdbc-hologres:compileTestJava`
   - Existing unit tests pass via `./gradlew 
:catalogs-contrib:catalog-jdbc-hologres:test -PskipITs`
   - Integration tests can be run by setting `GRAVITINO_HOLOGRES_JDBC_URL`, 
`GRAVITINO_HOLOGRES_USERNAME`, `GRAVITINO_HOLOGRES_PASSWORD` and running 
`./gradlew :catalogs-contrib:catalog-jdbc-hologres:test`


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to