Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
dusingh-c
Contributor II
Contributor II

Native Qlik Databricks connector having Data truncate issue post upgrading to Qlik Sense August 2023 Patch 14 from Patch 5

Hi All,

We have upgraded our Qlik Sense Enterprise on Windows to August 2023 Patch 14 from Patch 5 in accordance with the recommendation given here https://community.qlik.com/t5/Support-Updates/Qlik-Sense-Enterprise-for-Windows-New-Security-Patches...

However, post patching we have observed that one of the descriptive field value is getting truncated to 255 character only for a preexisting data connection created using native Qlik Databricks connector (QvODBCConnectorPackage). We do not have this issue when the Data connection is set up using ODBC DSN method (creating a DSN on server using Simba Spark ODBC driver and subsequently creating an ODBC connection in Qlik by selecting the System DSN). Please advise.

Best Regards

Labels (3)
4 Replies
Jack_Guo
Support
Support

Hi @dusingh-c , was the data truncate issue existing before with August 2023 Patch 5 via native Qlik Databricks connector (QvODBCConnectorPackage)? Can you confirm it was working fine but now doesn't work after updating patch from 5 to 14?

dusingh-c
Contributor II
Contributor II
Author

Hi @Jack_Guo , no the issue is observed only after updating to Patch14 from Aug 2023 Patch 5

Jack_Guo
Support
Support

Hi @dusingh-c 

do you have a DEV or TEST environment that can replicate the same issue with Qlik Sense August 2023 patch 14? if not, please log a support case with Qlik Support for further investigation.

dusingh-c
Contributor II
Contributor II
Author

Hi @Jack_Guo yes we are facing the same issue across all environments (dev/test/production) with August 2023 Patch 14, Support case with Qlik Support is already logged and awaiting updates from Qlik support Engineers in this regard.