PDA

View Full Version : pdi-4.3.0 to CDH 4.0.1. hive connection issue



rajpal
09-24-2012, 07:36 PM
I'm using "pdi-ce-4.3.0-stable" and trying to access "CDH-4.0.1" version of big data.
I followed http://wiki.pentaho.com/display/BAD/...+Cloudera+CDH4 (http://wiki.pentaho.com/display/BAD/Configure+Pentaho+for+Cloudera+CDH4) to configure kettle to support CDH-4, hoping that minor version change would work. After performing these operations, Kettle fails to connect with Hive. This tutorial talks about CDH-4.0.0 version and I have CDH-4.0.1.
It makes me wonder if CDH 4.0.1 is supported with kettle 4.3.0-CE or not? Also, workarounds, if any please share.

Thanks

rajpal
09-25-2012, 01:27 PM
Replaced hive-jdbc driver hive-jdbc-0.8.1-cdh4.0.1 in libext/jdbc with the jdbc driver shipped with pdi-4.3.0-ce. Now able to connect with Hive but getting error while reading data from hive. Table input step throws error for any select * statement as:

SELECT * FROM vendor where name = 'jugnu'

2012/09/25 10:25:07 - Table input.0 - ERROR (version 4.3.0-stable, build 16786 from 2012-04-24 14.11.32 by buildguy) :
2012/09/25 10:25:07 - Table input.0 - ERROR (version 4.3.0-stable, build 16786 from 2012-04-24 14.11.32 by buildguy) : Error getting row information from database:
2012/09/25 10:25:07 - Table input.0 - ERROR (version 4.3.0-stable, build 16786 from 2012-04-24 14.11.32 by buildguy) : Method not supported


Is there any updated driver which could avoid this issue??
Thanks,

rajpal
09-25-2012, 07:08 PM
Some more information.

Linux: 4.3.0-CE and chd4.0.1 works fine without any problem. Just copied cdh4.0.1. jars as explained in the tutorial for cdh-4.0.0. HBase and Hive connectivity/read works fine

Windows 7: 1. With changes similar to Linux(just replaced jars), unable to make HIve db connection.
2. Replaced libext/bigdata/JDBC/hive-jdbc-0.7.0-pentaho-1.0.1 with hive-jdbc-0.8.1-cdh4.0.1 and able to create connection with Hive db. However, unable to read data from Hive db using Table Input and SQL script. I'm not sure if replacing this is good idea or not. With table input getting previously reported error:

SELECT * FROM vendor where name = 'jugnu'

2012/09/25 10:25:07 - Table input.0 - ERROR (version 4.3.0-stable, build 16786 from 2012-04-24 14.11.32 by buildguy) :
2012/09/25 10:25:07 - Table input.0 - ERROR (version 4.3.0-stable, build 16786 from 2012-04-24 14.11.32 by buildguy) : Error getting row information from database:
2012/09/25 10:25:07 - Table input.0 - ERROR (version 4.3.0-stable, build 16786 from 2012-04-24 14.11.32 by buildguy) : Method not supported

Anyone, any clues??