Closed GaryLiuTelus closed 11 months ago
This has been resolved. the problem was caused by pointing HWC jar file to HDFS. After change the path back to edge node, it resolved. My original configuration is:
"session_configs":{
"jars":["hdfs://xxxx/xxx/hive-warehouse-connector-assembly-1.0.0.3.1.5.0-152.jar"]
}
Now my configuration:
"session_configs":{
"jars":["file:///yyy/yy/hive-warehouse-connector-assembly-1.0.0.3.1.5.0-152.jar"]
}```
Describe the bug A clear and concise description of what the bug is. When I use the following code to open a Hive managed table, it keeps running without returning any results back.
When checking the log, it said:
But actually, the JDBC Url should be
jdbc:hive2://qccr-hadoop-m001.oss.ads:2181,qccr-hadoop-m002.oss.ads:2181......
, which I have specified in the session_configs:But based on log, the session still try to use
jdbc:hive2://qccr-hadoop-m010.oss.ads:10501/
, instead ofjdbc:hive2://qccr-hadoop-m001.oss.ads:2181,qccr-hadoop-m002.oss.ads:2181......
, and so got a 401 error. Looks the configurations are not properly transferred.But it worked with non-managed tables well. like
And the same setting worked well in Zeppelin Livy interpreters, which can open ACID tables without issues.
To Reproduce Steps to reproduce the behavior.
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Versions:
Additional context Add any other context about the problem here.