Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Cause of DBVisulizer client error after turning on LZO/snappy compression?

avatar
Super Collaborator

Experts,

Has anyone encountered the exception below?

... Physical database connection acquired for: Hive QA1
15:03:16  [SELECT - 0 row(s), 0.000 secs]  [Error Code: 35, SQL State: S1000]  [Hortonworks][HiveODBC] (35) Error from Hive: error code: '0' error message: 'java.io.IOException: java.io.IOException: Cannot create an instance of InputFormat class org.apache.hadoop.mapred.TextInputFormat as specified in mapredWork!'.
... 1 statement(s) executed, 0 row(s) affected, exec/fetch time: 0.000/0.000 sec  [0 successful, 0 warnings, 1 errors]
 

I suspect it is caused by knox gateway server is missing lzo/snappy.

1. Executing same query on hive cli works fine
2. Checked Knox Gateway machine, /etc/hadoop/conf/core-site.xml does not have io.compression properties while the cluster(and all other nodes) has them.
3. knox gateway machine missing lzo/snappy packages/jars

Appreciate your quick input.

1 ACCEPTED SOLUTION

avatar
New Member

Check the logs from your HS2 instance. Knox is a proxy to HS2 (via HTTP JDBC/ODBC) so it doesn’t do anything that would present this error. That’s coming from HS2.

View solution in original post

1 REPLY 1

avatar
New Member

Check the logs from your HS2 instance. Knox is a proxy to HS2 (via HTTP JDBC/ODBC) so it doesn’t do anything that would present this error. That’s coming from HS2.