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

   ### What changes were proposed in this pull request?
   
   - `HiveServer2Sql` runs HiveQL over JDBC against the container's 
HiveServer2; `CatalogHiveViewIT` and `CatalogHive3IT` use it instead of `docker 
exec hive -S -e`. Adds `hive-jdbc` as a catalog-hive test dependency.
   - `HiveContainer` checks readiness without the Hive CLI: a live DataNode 
through the NameNode's JMX, the warehouse directory through WebHDFS, then the 
metastore and HiveServer2 ports. Kerberos Hive keeps the CLI path.
   - `HiveContainer.getHadoopUser()`: clients act as the user the container's 
processes run as (`HADOOP_USER_NAME`), as the CLI calls did.
   - Before Hadoop starts, the container lets that user impersonate users, 
which HiveServer2 needs for its sessions. The image change that makes this 
unnecessary is tracked in a follow-up issue.
   
   This PR includes the commits of the PRs below it. Review only its own 
commit: 
https://github.com/nevzheng/gravitino/compare/claude/13900-tc-09-durability...claude/13900-tc-10-hive-jdbc
   
   ### Why are the changes needed?
   
   Each `hive -e` call starts a JVM with its own embedded metastore: seconds 
per statement and per readiness poll. Locally (3 runs, medians): catalog-hive 
380 s → 235 s (−38 %), `CatalogHiveViewIT` 122 s → 37 s (−70 %), 
hive-metastore-common 164 s → 147 s (−10 %); Hive readiness 8 s → 0.5 s per 
start.
   
   Fix: #14049
   
   ### Does this PR introduce _any_ user-facing change?
   
   No. Test code only.
   
   ### How was this patch tested?
   
   catalog-hive, hive-metastore-common, catalog-fileset, filesystem-hadoop3, 
authorization-ranger and authorization-chain integration tests.
   
   **Stack:** #14005 → #14006 → #14007 → #14008 → #14009 → #14010 → #14011 → 
#14012 → #14013 → **#<PR 10>**
   


-- 
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