03-29-2018 12:23 AM
Is there a parameter in Impala ODBC driver that would define the number of characters/bytes fetched in a row. When I create a report in OBIEE with varchar/char/string characters, we loose one of the columns. But same size of report with int/bigint works fine. I suspect it could be because of the array size that loads a row. Any help would be appreciated. Thanks.
03-31-2018 04:37 AM - edited 03-31-2018 04:38 AM
I think you must change this param in your odbc.ini file:
StringColumnLength: The maximum number of characters that can be contained in STRING columns.
(default value: 32767).
04-02-2018 01:16 AM - edited 04-02-2018 01:18 AM
@AcharkiMed. Thanks a lot for your suggestion. I tried this parameter with default value and even tried adding few 0s to this. But still, its an issue. I do not see all the column values. Each report has a particular column, at different positions, that does not get displayed. This does not change. If column emp_name is not appearing in report A, it's always this column. But, this column value appears in another report, Report B which may also have all string fields. In Report B, it would be some other column in random order that disappears.
04-02-2018 01:59 AM
You are welcome man,
Do you work with CDH Impala ? if yes which release please ?
Give me the query that you run.
Also if it's possible try to active the odbc log and give us the whole logging file.
04-02-2018 02:15 AM
Will post the log files soon. Here are the versions and config for your reference
Description=Cloudera ODBC Driver for Impala
StringColumnLength = 32767
04-02-2018 07:30 AM
ok, so try to active the Impala ODBC driver log also active the unixODBC log and rerun the same test then send to me the two log files to have a clear vision on this issue.
To active impala odbc log, go to /opt/cloudera/impalaodbc/lib/64/cloudera.impalaodbc.ini and set this params:
To active unixODBC go to /opt/cloudera/impalaodbc/Setup/odbcinst.ini and add this two line: