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
Cloudera requires two connection types - Hive Server 2 and Impala. The "Register Server" dialog has changed to accommodate the Impala connection relative to Cloudera. It sets the default port to 21050 for Impala and 10000 for Hive Server 2. Also, locks the distribution to Cloudera when Impala is selected.
Additionally, Cloudera with Hive Server 2 supports complex data types.
Also ADS 14.0.14-1
Remember.. When testing, use the Cloudera JDBC drivers that came with the server. In my case..
hive-exec-0.10.0-cdh4.3.0, hive-jdbc-0.10.0-cdh4.3.0, hive-metastore-0.10.0-cdh4.3.0, hive-service-0.10.0-cdh4.3.0
Verified in ADS 15.0.0-dev-293
On Cloudera Quickstart VM CDH5 ,
a] Connected to Impala
Connection Type: Impala , Port : 21050
Also able to connect Cloudera HiveServer 2 [Hive 0.12]
b] Connected to HiveServer 2
Connection Type: HiveServer 2, Distribution: Cloudera, Port: 10000
Verified in ADS 15.0.0-dev-293
On Cloudera Quickstart VM CDH5 ,
a] Connected to Impala
Connection Type: Impala , Port : 21050
Also able to connect Cloudera HiveServer 2 [Hive 0.12]
b] Connected to HiveServer 2
Connection Type: HiveServer 2, Distribution: Cloudera, Port: 10000
Verified in ADS 14.0.15
and
in ADS 15.0.0-dev-306
Verified in ADS 14.0.15
and
in ADS 15.0.0-dev-306
Issue #12157 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build ADS 15.0.0-dev-290 |
| No time estimate |
Also ADS 14.0.14-1
Remember.. When testing, use the Cloudera JDBC drivers that came with the server. In my case..
hive-exec-0.10.0-cdh4.3.0, hive-jdbc-0.10.0-cdh4.3.0, hive-metastore-0.10.0-cdh4.3.0, hive-service-0.10.0-cdh4.3.0