Cognos connection to Hadoop

[Niranjan_9]

Hi team,
I am working on a POC on cognos 10.2.2 connection to Hadoop.\
When I try to connect to the DB, I am getting the below error, tried all possibilities but no help
XQE-JDB-0004 A problem occurred finding the driver class "org.apache.hive.jdbc.HiveDriver".
1. I have installed Cognos 10.2.2
2. Downloaded the JDBC drivers for cloudera (got the details from hadoop dev team) .
3. Set the class path and placed the jar files in the p2pd/web-inf/lib
4. created a JDBC connection with a Hive connector and updated the URL to reflect the port number/dbname.
[jdbc:hive2://paehowchq1e02:10000/default]
Any help is highly appreciated. Thanks

[MFGF]

Hi team,
I am working on a POC on cognos 10.2.2 connection to Hadoop.\
When I try to connect to the DB, I am getting the below error, tried all possibilities but no help
XQE-JDB-0004 A problem occurred finding the driver class "org.apache.hive.jdbc.HiveDriver".
1. I have installed Cognos 10.2.2
2. Downloaded the JDBC drivers for cloudera (got the details from hadoop dev team) .
3. Set the class path and placed the jar files in the p2pd/web-inf/lib
4. created a JDBC connection with a Hive connector and updated the URL to reflect the port number/dbname.
[jdbc:hive2://paehowchq1e02:10000/default]
Any help is highly appreciated. Thanks

Quick sanity check. Have you restarted the Cognos service since copying the jar files into p2pd\web-inf\lib? The error you posted seems to show Cognos can't see the JDBC jar files - they need to be there when the service starts for it to be able to see them.

Cheers!

MF.

[Niranjan_9]

Hi MF, Thanks for the reply. Appreciate taking time to reply.

Sorry, I Missed to mention , yes I did a restart of the services.(all went fine and no errors)
Also, I did try giving a wrong db name or wrong port number, but the error remains the same.
So , somehow those drivers are not being picked by Cognos.

Also, I tried editing the environmental variables manually, but did not help.

[MFGF]

Hi MF, Thanks for the reply. Appreciate taking time to reply.

Sorry, I Missed to mention , yes I did a restart of the services.(all went fine and no errors)
Also, I did try giving a wrong db name or wrong port number, but the error remains the same.
So , somehow those drivers are not being picked by Cognos.

Also, I tried editing the environmental variables manually, but did not help.

You could try copying the jar files into v5dataserver\lib too (then restarting) to see if this makes a difference?

MF.

[Niranjan_9]

yes, that step did not help either.
Thanks

[smiley]

https://www.youtube.com/watch?v=FPwUAiFE0Q8

[Niranjan_9]

HI Everyone,
I am able to achieve a successful connection to Impala, following the above steps.
Now, I want to have a connection using Hive connector, but I see in the JDBC driver download page of cloudera
http://www.cloudera.com/downloads/connectors/hive/jdbc/2-5-16.html , that it is supported only with Impala.

Can anyone let me know if they had a both Hive and Impala connections to Hadoop.
Also , the Jar files available in the downloads are the same, so how can we achive this. Any help is highly appreciated.

The only reason this is needed because of few of the data types of my existing framework manager are supported using Hive and not Impala.

thanks very much.

[the6campbells]

The Cloudera JDBC driver for Hive is not supported in Cognos BI/Analytics.

Instead, you must obtain the JAR files the your CDH host ships with that would be the Apache Hive JDBC driver.

The driver is actually a set of JAR files.

For example, if you were using CDH 5.5 you could get the JAR files for:

standalone JDBC driver: hadoop-auth, hadoop-common and hive-jdbc
non-standalone: commons-logging, hadoop-common, hadoop-core, hive-exec, hive-metastore, hive-service, httpclient, httpcore, libfb303, libthrift, log4j, slf4j and slf4j-log

Keep in mind for the non-standalone driver some of the jar files are optional if you are not planning to use kerberos

For more details on the JAR files etc, I would recommend you ask your distribution vendor to point you to their documentation or confirm where you would locate the jars if you cannot find them.