Forum Discussion

tobazan's avatar
tobazan
Frequent Visitor
1 year ago
Solved

Python (not spark) Notebook exitValue issue

Is it a known issue that plain Python notebooks in Fabric don't return exitValue as expected?   I tried ```notebookutils.notebook.exit(json.dumps(json-object))``` as an alternative to the msspark...
workspaces
  • Anonymous's avatar
    Anonymous
    1 year ago

    Hi tobazan,

     

    Explicit Output Management: Instead of relying on the exit() method, store the output in a predefined location that the pipeline can read, e.g., Azure Blob Storage or a SQL database.

     

    Regards,

    Vinay Pabbu

Anonymous's avatar
Anonymous
Not applicable
1 year ago

Hi tobazan,

 

Thank you for reaching out to Microsoft Fabric Community Forum.

 

The issue likely arises because plain Python notebooks in Fabric do not fully support the notebookutils.notebook.exit() method for returning exit values, unlike PySpark notebooks. The output may not propagate correctly due to pipeline configuration or limitations in handling Python notebook exits within Fabric.

 

You need to ensure the pipeline is set up to capture outputs and consider using alternative methods like manual error handling or explicit output management within the notebook itself.

 

Please le me know if you have any additional questions.


Did I answer your question? Mark my post as a solution, this will help others!
If my response(s) assisted you in any way, don't forget to give "Kudos"

 

Regards,
Vinay Pabbu