Forum Discussion
Failed to complete the command because the underlying location does not exist.
I have some table shortcuts created in a lakehouse. The source is ADLSG2. The tables are being updated daily from jobs in databricks. When I query one of the table shortcuts a day after creating the shortcut it gave me this error.
Failed to complete the command because the underlying location does not exist. Underlying data description: table 'lakehouseschema.lakehousetableshortcut', file 'https://onelake.dfs.fabric.microsoft.com/workspaceid/lakehouseid/Tables/lakehouseschema/lakehousetableshortcut/partitionColumn=1000/part-00000-*.snappy.parquet '.
I checked the file inside the partiton and it was not there. How to resolve this issue as the table is being used in multiple pipelines? Kindly help.
Hi suparnababu8 - That is excatly what I tried. The refresh failed for the table without any specific error ('code': 'SqlErrorNumber', 'message': '24550'). Finally I had to delete and recreate the shortcut table. Then I ran a refresh, which was successful. Then I ran the query and it ran without any issue. Only problem was that, when I ran the same query in databricks, it ran quickly but using sql endpoint, it took forever.
3 Replies
v-sdhruvCommunity Support
Hi abhilash_o_p ,
It’s great to hear that recreating the shortcut table resolved the refresh issue and that the query now runs successfully. The performance difference between Databricks and the SQL endpoint is definitely worth noting—thanks for highlighting that.
If you haven’t already, could you please mark your post as the accepted solution? It’ll help others facing similar issues find the resolution more easily.
Thank you!- suparnababu8
Super User
Hi abhilash_o_p
I think it's becuase of shortcuts not syncing the data updation after your Databricks job run. Just refresh the shortcut in lakehouse. Try this and let me know if it works.
Thank you!
Did I answer your question? Mark my post as a solution!
Proud to be a Super User!Hi suparnababu8 - That is excatly what I tried. The refresh failed for the table without any specific error ('code': 'SqlErrorNumber', 'message': '24550'). Finally I had to delete and recreate the shortcut table. Then I ran a refresh, which was successful. Then I ran the query and it ran without any issue. Only problem was that, when I ran the same query in databricks, it ran quickly but using sql endpoint, it took forever.
