Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
Aqua Data Studio 15.0.11-10
Build #: 41835
Built on: 2015-Jan-15 11:29:41 AM
OS: Ubuntu 14.04
Database : Cloudera Hive [CDH5.2]
Drivers: Simba drivers
Issue: Driver class name doesn't get updated in Server registration window Drivers Tab
Steps to reproduce the issue:
1. Connect ADS15 to Cloudera CDH5.2 using Simba drivers
Credentials:
Name: CDH52HiveHS2Simba-ADS15
Authentication Type: No Authentication
Connection Type: HiverServer 2
Distribution: Cloudera
Host: Enter IP
Port: 10000
Database: Default
Click on 'Save' button.
2. Right click on this server, select 'Server Properties', Click on Drivers Tab,
Observe the Driver field: com.aquafold.aquacore.open.rdbms.drivers.hive.AQHiveDriver2
In ADS 16 Driver class name shown properly
Expected: com.cloudera.hive.jdbc4.HS2Driver
Please compare screenshots: Screenshot1-Hive-ADS16.png and Screenshot3-Hive-ADS15.png .
Same thing also applicable for Impala connection.
|
|
190 KB
|
|
243 KB
Hi Anil, This change in V16 behavior was as a result of issue 12530. In order for me to to display the current Hive driver class in the new server support information panel, I had to store the current dynamic driver, when loaded, instead of the static AQHiveDriver. To be consistent, I stored it in a local variable like all the other databases. The Driver tab in the Server Properties benefited from this change in that it now has the correct dynamically loaded driver class. Issue 12530 is not going to be retrofitted to V15. It is a V16 feature
Issue #13050 |
| Closed |
| Won't Fix |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
1 issue link |
relates to #13029
Issue #13029Hive - Retrofit changes from V16 to V15 to handle Cloudera Simba drivers. |
Hi Anil, This change in V16 behavior was as a result of issue 12530. In order for me to to display the current Hive driver class in the new server support information panel, I had to store the current dynamic driver, when loaded, instead of the static AQHiveDriver. To be consistent, I stored it in a local variable like all the other databases. The Driver tab in the Server Properties benefited from this change in that it now has the correct dynamically loaded driver class. Issue 12530 is not going to be retrofitted to V15. It is a V16 feature