Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
ALERT: QlikView server communication interruptions following Microsoft Windows Domain Controller security updates

Qlik Replicate: DEFAULT_FILE_NOT_FOUND Error

100% helpful (1/1)
cancel
Showing results for 
Search instead for 
Did you mean: 
shashi_holla
Support
Support

Qlik Replicate: DEFAULT_FILE_NOT_FOUND Error

Last Update:

Aug 6, 2024 1:47:39 AM

Updated By:

Sonja_Bauernfeind

Created date:

Aug 6, 2024 1:47:39 AM

Qlik has observed the following error while working with Databricks Delta Lakehouse endpoint in Replicate 2023.05 or above. This Technical Advisory article aims to create awareness of the issue and provides a workaround. 

[DEFAULT_FILE_NOT_FOUND] It is possible the underlying files have been updated. You can explicitly invalidate the cache in Spark by running 'REFRESH TABLE tableName' command in SQL or by recreating the Dataset/DataFrame involved. If disk cache is stale or the underlying files have been removed, you can invalidate disk cache manually by restarting the cluster.

This causes the table to be suspended and requires a reload.


Environment:

  • Qlik Replicate 2023.05 and later

Resolution

Fix Version:

A fix is currently being worked on and patches will be made available at the earliest.

Workaround:

  1. Go to the Databricks Endpoint
  2. Open the Advanced tab
  3. Open Internal Paramters
  4. Add the parameter: additionalConnectionProperties
  5. Set the value toForceSynchronousExec=1

    additionalConnectionProperties.png

  6. Save the Endpoint
  7. Stop and Resume the task

 

Information provided on this defect is given as is at the time of documenting. For up to date information, please review the most recent Release Notes, or contact support with the ID QB-28166 for reference.

Cause

Product Defect ID: QB-28166

Labels (1)
Version history
Last update:
‎2024-08-06 01:47 AM
Updated by: