Forum Discussion
Spark Environment Properties not applied during runtime from Pipeline Notebook Activity
Hi jisaac
unlike Databricks, Microsoft Fabric doesn't currently support initialization scripts for Spark environments. In Databricks, these scripts let you apply settings automatically when a cluster starts, but Fabric doesn’t offer that feature yet.you can manually set the Spark configs at the top of each notebook to ensure the necessary settings (like handling pre-1900 timestamps) are always applied. Alternatively, if you disable High Concurrency mode in pipeline runs, each notebook will start a fresh Spark session and correctly pick up the environment settings.
Another option is to create a small helper notebook that contains all your spark.conf.set(...) lines and use %run at the top of your main notebooks. This way, you keep things consistent without repeating code everywhere.
If the issue still persists we recommend you to raise a support ticket.You can submit a ticket through the Microsoft Power BI Support Portal:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Thank you.
Two things that I observe that are inconsistent with what you've said and confuse me:
- Whether the session starts from the first or second notebook run, it should still be using the same default properties, no? Both notebooks are set to run with the same environment. Are you saying that high concurrency sessions always start with no environment or properties?
- The settings are clearly not carrying over from one notebook to another. Observe the screen shots of two notebooks run under one HC session.
First notebook run:
Second notebook run, settings are not changed from previous run:
The settings reverted in the second notebook, so they are clearly being reset between notebooks.
Thanks for coming back.
so you have disabled the high concurrency mode. Still properties are not set in Notebook through pipeline.
The point I was trying to make through high concurrency was that if the first session started without those properties set, it will remain like that even if you change the spark initial properties in UI.