I'll try to attach the log files using another browser in a reply.DBeaver is a free, open source multiplatform database management tool and SQL client for developers and database administrators. Each has 2 connections, since Dbeaver opens a separate connection for the metadata. The one with DEBUG ON and the one with TRACE ON. Now if I open a specific database, expand it and click to expand the table names, the debug version expands just the first table, the trace version display all the 3 tables.I expand the HIVE tree and it lists all my databases names.It opens a tree with a node HIVE below it I expand the Datalake connection so it connects.If the log level is TRACE it works fine, if it is DEBUG or higher, it fails. ¯\_(ツ)_/¯Īnd now the weird behavior happens. The admin powers were removed from my user, but now I can change the "Logging Options" and they are persisted. So, with admin powers, I went to the ODBC admin, confligured the log level to trace at the "Logging Options" above and it worked.Īfter editing the log level, these lines were automatically added to the ODBC.INI file:ĭriver32=C:\Program Files\Cloudera ODBC Driver for Apache Hive\lib\ClouderaHiveODBC64.dll I edited the odbc.ini to add the recommended log config: The sysadm gave admin permissions to my user. I also can't edit the file "C:\Windows\odbc.ini". If I try to configure it again the log level is off. %windir% \syswow64\odbcconf configdsn "Cloudera ODBC Driver for Apache Hive" "DSN= Datalake |DESCRIPTION=Driver datalake|HiveServerType=2|ServiceDiscoveryMode=ZooKeeper|ZKNamespace=hiveserver2|Host=zookeeper01:2181,zookeeper02:2181,zookeeper03:2181|Port=10000|Schema=default|AuthMech=1|KrbRealm=S.NET|KrbServiceName=hive|ServicePrincipalCanonicalization=0|KrbHostFQDN=_HOST|GetTablesWithQuery=1|InvalidSessionAutoRecover=0|AutoReconnect=1"Īfter the install, I open the Windows ODBC Admin and try to change the log level in "my datasource" -> Configure button -> Logging Options the option isn't persisted. exec.DBCException: SQL Error : Comprimento inválido de cadeia de caracteres ou de bufferĪt .JDBCAbstractValueHandler.fetchValueObject(JDBCAbstractValueHandler.java:55)Īt .(ResultSetDataReceiver.java:125)Īt .fetchQueryData(SQLQueryJob.java:718)Īt .executeStatement(SQLQueryJob.java:541)Īt .lambda$0(SQLQueryJob.java:441)Īt .(DBExecUtils.java:171)Īt .executeSingleQuery(SQLQueryJob.java:428)Īt .extractData(SQLQueryJob.java:813)Īt .$QueryResultsContainer.readData(SQLEditor.java:3280)Īt .$0(ResultSetJobDataRead.java:118)Īt .(ResultSetJobDataRead.java:116)Īt .$n(ResultSetViewer.java:4624)Īt .(AbstractJob.java:105)Īt .(Worker.java:63)Ĭaused by: : Comprimento inválido de cadeia de caracteres ou de bufferĪt .createSQLException(JdbcOdbc.java:6964)Īt .standardError(JdbcOdbc.java:7121)Īt .SQLGetDataString(JdbcOdbc.java:3914)Īt .getDataString(JdbcOdbcResultSet.java:5697)Īt .getString(JdbcOdbcResultSet.java:353)Īt .getObject(JdbcOdbcResultSet.java:1677)Īt .getObject(JDBCResultSetImpl.java:627)Īt .JDBCStringValueHandler.fetchColumnValue(JDBCStringValueHandler.java:52)Īt .JDBCAbstractValueHandler.fetchValueObject(JDBCAbstractValueHandler.java:49)īefore this stack trace there is a message `Can't read column 'tab_name' value`: The error message above is in Brazilian Portuguese: Here is the complete stack trace displayed in the Error Log. exec.DBCException: SQL Error : Invalid string or buffer length If I run the command show tables from raw_aneel, DBeaver interface will display: When I open DBeaver, The dabase just shows the table `localizacao`: All my databases just display a few of it's tables. Any help to solve or debug this problem would be greatly appreciated. I'm connecting to Hive using Cloudera's ODBC driver version 2.6.9 and I'm getting a weird behavior that ruins the user experience.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |