Shortcut maintenance

[DennesTorres]

Hi,

I noticed the following situation:

Considering I have a shortcut in one lakehouse and an object built using this shortcut in another lakehouse or data warehouse (a view, for example).

If I drop the shortcut before dropping the view, I can't drop the view anymore, not even if I create the shortcut again.

The message below shows an error after 4 minutes of execution trying to drop a view. This was not the only occurrency..

Another common error message happens when refreshing the objects, after the drop attempt:

Kind Regards,

Dennes

[Anonymous]

Hi @DennesTorres ,

Thanks for using Fabric Community.

Can you please help me understand how you were able to land into this scenario?
I would like to know how you were accessing shortcut in one lakehouse from another lakehouse/warehouse.
Could you please share detail steps so that I can reproduce the issue at my end and can check with the team.

[DennesTorres]

Hi,

Sorry for the late reply.

I repeated the scenario at this exact moment to explain a step by step:

Lakehouse A has a table product

Lakehouse B creates a shortcut to table product on lakehouse A

Lakehouse C creates a shortcut to the shortcut of table product in Lakehouse B

Once everything is created, goes to Lakehouse B and drop the shortcut. This leaves the object on lakehouse A "orphan".

The result I received at the moment is the following image:

There is no "Delete" option:

Trying the option "move to files" doesn't work as well:

This happened with data warehouses as well. If I have a data warehouse on the same workspace as lakehouse C, I can create a view in the data warehouse using the shortcut table in lakehouse C. When the shortcut on B is dropped, everything becomes "orphan" and "stuck".

Kind Regards,

Dennes

Kind Regards,

[Anonymous]

Hi @DennesTorres ,

You can delete the shortcut from child folder, see the screenshot for your reference.

After deleting:

Hope it is helpful. Please let me know incase of any queries.

[DennesTorres]

Hi,

Correct. My bad, this one was easy.

But let's consider a warehouse D on the scenario. 

A view is created on the warehouse D using a table on the lakehouse C. This table is a shortcut to the lakehouse B which is a shortcut to the lakehouse A.

If the shortcuts are broken, things get very strange. This happened to me. Until today (tested exactly now), if I get into the warehouse and make a refresh on the views folder, the following error happens:

It's the same described on the first message. Once it happened, the error continues there on every refresh on the views folder.

Kind Regards,

Dennes

[Anonymous · Accepted solution]

Hi @DennesTorres ,

I didnot find any challenge in dropping the view from lakehouse_D.

lakehouse_A : Main Table
lakehouse_B : Shortcut created from Main Table (present in lakehouse_A)

lakehouse_C : Shortcut created from Shortcut Table (present in lakehouse_B)
lakehouse_D : View created for Shortcut Table (present in lakehouse_C)

Able to preview the view and everything works proper.

Deleted Shortcut Table (present in lakehouse_b) and then drop the view (present in lakehouse_D) which got executed perfectly.

Hope it is helpful.

[DennesTorres]

Hi,

Well, my guess is the problem got solved at some update, while my DW on which I tried to drop a view before the solution got "stuck" on something.

I will investigate a bit more and discover if I need to open a support ticket.

Kind Regards,

Dennes

[Anonymous]

HI @DennesTorres ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.
In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.

[Anonymous]

Hi @DennesTorres ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.
In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.