Forum Discussion
Select the fabric kernel to debug spark job definition in VSCode
- 1 year ago
Currently, Spark Job Definitions cannot be debugged using the Fabric kernel in VSCode. The Fabric kernel is mainly designed for running notebooks, whereas Spark Job Definitions require execution on the remote Spark Runtime. If you try to debug a Spark Job Definition using the Fabric kernel, it won’t function as expected since it lacks the necessary Spark execution environment.
To properly develop and debug Spark jobs, you need to select the remote Spark Runtime, which provides the required Spark components and dependencies. This ensures that your job runs in an environment similar to the one it will be deployed in, allowing for accurate testing and debugging.
If you were expecting this functionality within the Fabric kernel itself, it would be worth checking Microsoft’s official roadmap or documentation for any future support. Having the ability to debug Spark Job Definitions directly in the Fabric kernel would be a valuable enhancement, as it would streamline development and testing workflows without requiring an external runtime.
Are there any specific issues you’re facing while debugging your Spark Job Definition? Let me know how I can assist further!
Hi Broeks,
Apologies for the inconvenience.
I regret the misunderstanding of the scenario. As mentioned in the document, it should also work for Spark job definition.
However, I am unable to reproduce the scenario. Therefore, I kindly request you to raise a support ticket for resolution using the link provided below. A dedicated backend team will assist you in resolving the issue.
Microsoft Fabric Support and Status | Microsoft Fabric
Thank you for your patience and understanding.
- Broeks1 year ago
Helper II
Thanks for your response.
I've created a support ticket.
This would help our use case to develop our own pyspark solution.
Are there any insights you can give me on what to expect for any further integration between fabric/spark and VSCode?