is there character length limit? : nchar(x) < 32700

[ianmcook]

is there character length limit? : nchar(x) < 32700

[ianmcook]

Hi @Curycu, the release notes for the new Impala ODBC driver version 2.6.11 indicates that this issue has been fixed:

[IMP-789][00208980] The driver imposes a minimum (255) and maximum (32,767) character length for the StringColumnLength connection property.
This issue has been resolved. The minimum limit has been set to 1 and values larger than 32,767 can now be set.

See https://docs.cloudera.com/documentation/other/connectors/impala-odbc/2-6-11.html.

[ianmcook]

Hi @Curycu, I was able to reproduce this issue in which STRING columns are truncated to 32767 characters. This is caused by the Cloudera ODBC Driver for Impala. Two possible solutions are:

• Upgrade to a newer version of the ODBC driver. I believe (but I am not certain) that this limitation has been resolved in the latest version of the ODBC driver.
• Set the variable StringColumnLength in your ODBC configuration. For example, if you're using an odbc.ini file, then add a line like this in it:

StringColumnLength=32767

Set the value to a larger number to enable longer STRING columns.

If neither of these solutions works for you, you might want to open a ticket with Cloudera and our support staff can investigate further.

[ianmcook]

Thanks. If you email me at ian at cloudera dot com I'll make sure your support ticket gets attention.

[ianmcook]

Hi @Curycu, could you tell me which driver you are using to connect to Impala (ODBC or JDBC) and what the version of the driver is? Thanks!

[Curycu]

R version 3.6.1 (2019-07-05)
Platform: x86_64-apple-darwin15.6.0 (64-bit)
Running under: macOS Catalina 10.15.5

Cloudera ODBC Driver for Impala (ClouderaImpalaODBC.dmg : $driver_version_sb$: 2.6.5.1005)

[Curycu]

upgrade to 2.6.10 odbc version & add StringColumnLength variable but still same problem occurs..
so I'll open a ticket. thank you for your kind help.

[Curycu]

@ianmcook thank you for your notice!