Forum Discussion

ToddChitt's avatar
ToddChitt
Super User
2 years ago
Solved

Notebook fails with error 200 when run from Pipeline

I'm fairly new to Spark Notebooks. I have one that dumps a JSON file into a couple of tables in my Lakehouse. It works fine when the Notebook is run on its own. But when I try to run it from the cont...
data engineering
  • Anonymous's avatar
    Anonymous
    2 years ago

    Hi ToddChitt 

    Thanks for the details. Can you please send me the code which you are running in the notebook? I will try to repro this from my side and let you know.

    And also can you please try to create a new notebook and then attach the lakehouse. Now try to run this notebook from the pipeline. If the issue still persists please do let me know. This way there wont be a grey out option and you can attach or detach the lakehouse.


    Did you try to set the target lakehouse as the default lakehouse? Default lakehouse is identified by the pin icon.

     



    Thanks.

Anonymous's avatar
Anonymous
Not applicable
2 years ago

Hi ToddChitt 

Thanks for the code. Glad that your query got resolved. Please continue using Fabric Community for any help regarding your queries.

ToddChitt's avatar
ToddChitt
Super User
2 years ago

I would consider this a bug: A Notebook created from the context of a Lakehouse has trouble access that lakehouse when run from inside a Pipeline. But a Notebook created on its own, with the Lakehouse added afterwards has no issues. 

 

Please don't tell me that this was "by design"!

 

  • dpombal's avatar
    dpombal
    Post Partisan
    2 years ago

    This is clearly a bug, I managed to make it work creating a new empty notebook , but this should be fixed

    • Anonymous's avatar
      Anonymous
      Not applicable
      2 years ago

      I also experienced this issue and agree it is a bug. However an alternative workaround to creating a new notebook is to completely remove and add the linked lakehouse back. To do this you can select the default pinned lakehouse and select Remove all Lakehouses. Once added back it seems to trigger from pipeline with no errors.