Select default lakehouse in notebook causes the DB collection to show wrong lakehouse (DBs) list

[kobia10]

When selecting default lakehouse from workspace A in a Fabric notebook, then executing 'show databases' sql command we see only the lakehouses (dbs) of the workspace A in which the default lakehouse belongs to.

Which also means that the notebook code cannot execute now against the other DBs and their tables

[Anonymous]

Hi @kobia10 ,

Thanks for using Fabric Community.
I tried to repro your scenario and this is my observation -

Yes you are correct, on executing 'show databases' sql command, we see only the lakehouses (dbs) of the workspace in which the default lakehouse belongs to. 

I would like to understand what is your issue and your expected result here? Please help me understand your problem more clearly, so I can guide you better.

[kobia10]

Expections are to see all LH (aka DBs) I am allowed to see/use.

I have a scenario in which spark code needs to execute against two LHs  (L1,L2) in different workspaces (W1,W2). 

if a spark sql code creates a join between two tables L1.table and L2.table, the code fails as it cannot access one of the tables

It is not clear why the helper 'default LH' functionality enforces wrong security on the Items

[Anonymous · Accepted solution]

Hi @kobia10 ,

At present this is by design and you will be able to see lakehouses present in default workspace only.

However, your suggestion is definitely valuable! We use customer feedback like yours to prioritize future features. The more users who request the ability to customize backgrounds, the higher it moves on our list.

Appreciate if you could share the feedback on our Microsoft Fabric Ideas. Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.

I hope this information helps. If you have any further queries please do let us know.

[Anonymous]

Hi @kobia10 ,

We haven’t heard from you on the last response and was just checking back to see if your query was answered.
Otherwise, will respond back with the more details and we will try to help .

Thanks

[Anonymous]

Hi @kobia10 ,

We haven’t heard from you on the last response and was just checking back to see if your query was answered.
Otherwise, will respond back with the more details and we will try to help .

Thanks