Forum Discussion
VSCode - Connecting to lakehouse and coding aid
Hi kjellvs ,
Apologies for the delay in response. This error is expected behavior with the existing version of Fabric lakehouse. I filed a bug for reading reference lakehouse in VS Code and the team is working on fixing the issue ASAP.
We are reaching out to the internal team to get more information related to ETA and will get back to you as soon as we have an update.
Stay tuned for more updates.
Thanks.Hi kjellvs ,
I will update you once I receive the information from the internal team. You can go ahead and close the ticket.
Thank you.
hi Anonymous,
Thank you for your swift reply. I took a bit longer over the weekend.
The first problem seems to be solved for the "defaultLakehouse", i.e., I am able to query tables from the lakehouse configured in fabric, shown next to the two arrows. However, I have two lakehouses currently referenced in my notebook (Raw data and processed data). I would like to access both from the notebook, however this does not seem possible, as I still get the similar error for the referenced lakehouse, which is not the default (java.lang.ClassNotFoundException: Failed to find data source: RawData. Please find packages at).
(metadata of the notebook according to vscode).
Is there a way to access both?
Besides this, I was also running into an issue where the kernel wasn't properly initialized. I am checking this by printing the "spark" variable. Restarting kernal/vscode sometimes was necessary for complete fix. If there are any other ways to fix this, let me know!
For the extension, you are right, I am using this one. I added the following at the top to make the extension also understand the predefined variables.
from pyspark.sql import SparkSession
spark: SparkSession Hope you can help me further.
Kjell
Hi kjellvs ,
Apologies for the delay in response. This error is expected behavior with the existing version of Fabric lakehouse. I filed a bug for reading reference lakehouse in VS Code and the team is working on fixing the issue ASAP.
We are reaching out to the internal team to get more information related to ETA and will get back to you as soon as we have an update.
Stay tuned for more updates.
Thanks.Hi kjellvs ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. Please let me know if you have any further queries.hi Anonymous,
as I understood from your previous response, there is no resolution yet as your team is working on fixing the issue ASAP, and that I should stay tuned. I guess this answers my questions, should I close the ticket in the mean time? Where could I find an update on this once this has progressed?
Kind regards,
Kjell