Forum Post: Re: Error when connecting to HiveServer using DataDirect ODBC driver

Status
Not open for further replies.
A

artiintell

Guest
The customer I am working with is running an Apache Hive 0.11 as far as I am aware and they run HiveServer not HiveServer2 (they do not want to run HiveServer2 for some reasons). I have enabled ODBC trace and managed to get some information which may be helpful and is the following: ENTER SQLSetEnvAttr SQLHENV 0x00000000642110 SQLINTEGER 200 SQL_ATTR_ODBC_VERSION SQLPOINTER 3 SQLINTEGER -6 EXIT SQLSetEnvAttr with return code 0 (SQL_SUCCESS) SQLHENV 0x00000000642110 SQLINTEGER 200 SQL_ATTR_ODBC_VERSION SQLPOINTER 3 SQLINTEGER -6 ENTER SQLAllocHandle SQLSMALLINT 2 SQL_HANDLE_DBC SQLHANDLE 0x00000000642110 SQLHANDLE * 0x0000000063cdf8 EXIT SQLAllocHandle with return code 0 (SQL_SUCCESS) SQLSMALLINT 2 SQL_HANDLE_DBC SQLHANDLE 0x00000000642110 SQLHANDLE * 0x0000000063cdf8 ( 0x00000000644080) ENTER SQLDriverConnect HDBC 0x00000000644080 HWND (nil) UCHAR * 0x007f8ae62b4b84 [4294967293] "******" SWORD -3 UCHAR * 0x007f8ae62b4b84 SWORD 6 SWORD * 0x007ffff3aefcde UWORD 0 SQL_DRIVER_NOPROMPT EXIT SQLDriverConnect with return code -1 (SQL_ERROR) HDBC 0x00000000644080 HWND (nil) UCHAR * 0x007f8ae62b4b84 [4294967293] "******" SWORD -3 UCHAR * 0x007f8ae62b4b84 SWORD 6 SWORD * 0x007ffff3aefcde UWORD 0 SQL_DRIVER_NOPROMPT ENTER SQLGetDiagRec SQLSMALLINT 2 SQLHANDLE 0x00000000644080 SQLSMALLINT 1 SQLCHAR * 0x007ffff3aef450 (NYI) SQLINTEGER * 0x007ffff3aef458 SQLCHAR * 0x007ffff3aef040 (NYI) SQLSMALLINT 1024 SQLSMALLINT * 0x007ffff3aef45c EXIT SQLGetDiagRec with return code 0 (SQL_SUCCESS) SQLSMALLINT 2 SQLHANDLE 0x00000000644080 SQLSMALLINT 1 SQLCHAR * 0x007ffff3aef450 [ 5] "HY000" SQLINTEGER * 0x007ffff3aef458 (6) SQLCHAR * 0x007ffff3aef040 [ 86] "[XXXX][ODBC Apache Hive Wire Protocol driver][Hive]Internal error processing clean" SQLSMALLINT 1024 SQLSMALLINT * 0x007ffff3aef45c (86) ENTER SQLGetDiagRec SQLSMALLINT 2 SQLHANDLE 0x00000000644080 SQLSMALLINT 2 SQLCHAR * 0x007ffff3aef450 (NYI) SQLINTEGER * 0x007ffff3aef458 SQLCHAR * 0x007ffff3aef040 (NYI) SQLSMALLINT 1024 SQLSMALLINT * 0x007ffff3aef45c EXIT SQLGetDiagRec with return code 100 (SQL_NO_DATA_FOUND) SQLSMALLINT 2 SQLHANDLE 0x00000000644080 SQLSMALLINT 2 SQLCHAR * 0x007ffff3aef450 (NYI) SQLINTEGER * 0x007ffff3aef458 SQLCHAR * 0x007ffff3aef040 (NYI) SQLSMALLINT 1024 SQLSMALLINT * 0x007ffff3aef45c ENTER SQLFreeHandle SQLSMALLINT 2 SQL_HANDLE_DBC SQLHANDLE 0x00000000644080 EXIT SQLFreeHandle with return code 0 (SQL_SUCCESS) SQLSMALLINT 2 SQL_HANDLE_DBC SQLHANDLE 0x00000000644080 ENTER SQLFreeHandle SQLSMALLINT 1 SQL_HANDLE_ENV SQLHANDLE 0x00000000642110 EXIT SQLFreeHandle with return code 0 (SQL_SUCCESS) SQLSMALLINT 1 SQL_HANDLE_ENV SQLHANDLE 0x00000000642110 I will also ask them to enable logging on a server side. It will be very much appreciated if you can point me to what needs to be configured and where to start logging info that can help us to identify the problem. Many Thanks, On Wed, Mar 25, 2015 at 12:02 PM, csands bounce-csands@community.progress.com wrote: RE: Error when connecting to HiveServer using DataDirect ODBC driver Reply by csands To get that message, the driver thinks it is running against a hive 1 server. Is this what you intend to do? If so, can you tell me the vendor and version of the hive server i.e. Apache 0.12, Cloudera 0.12.05 Hive2 is a more stable, multi user server. You should consider using it. Also as of Hive 1.0, the hive server 1 is no longer supported by Apache. If it is a hiver 2 server. Change the WireProtocolVersion connect setting to 2 (hive server 2) And see if that fixes your problem. From: Phil [mailto: bounce-pprudich@community.progress.com ] Sent: Tuesday, March 24, 2015 5:07 PM To: TU.DD.Connect@community.progress.com Subject: RE: [Technical Users - DataDirect Connect] Error when connecting to HiveServer using DataDirect ODBC driver RE: Error when connecting to HiveServer using DataDirect ODBC driver Reply by Phil That error comes from the server itself. Was there more to the message? Some versions of the server appear to provide more followup information which may be of use. Alternatively, you may need to consult your server log files if you haven't done so already to see if more information may be available there. Hope this helps, Phil Stop receiving emails on this subject. Flag this post as spam/abuse. Stop receiving emails on this subject. Flag this post as spam/abuse.

Continue reading...
 
Status
Not open for further replies.
Top