Forum Discussion

SørenBrandt's avatar
SørenBrandt
Frequent Visitor
1 year ago
Solved

400 error when accessing lakehouse files from notebook

Hi all! Pretty much every day, I experience spurious errors when accessing (csv) files in a notebooks default lakehouse. By spurious, I mean that they may happen in one session, but then later the s...
notebook
  • Anonymous's avatar
    Anonymous
    1 year ago

    Hi SørenBrandt 

     

    You may try reading the CSV file with ABFS path instead and check whether this will be more reliable. This could avoid failures in a scenario that the default lakehouse might be changed.

     

    Best Regards,
    Jing
    Community Support Team

Anonymous's avatar
Anonymous
Not applicable
1 year ago

Hi SørenBrandt 

 

You may try reading the CSV file with ABFS path instead and check whether this will be more reliable. This could avoid failures in a scenario that the default lakehouse might be changed.

 

Best Regards,
Jing
Community Support Team

  • SørenBrandt's avatar
    SørenBrandt
    Frequent Visitor
    1 year ago

    Hi Anonymous ,

    Thankyou for your suggestion 👍. I have changed to using the ABFS path, and right now it seems to be going through on first attempt. However, since this has been a bit unpredictable, I will keep trying to see if the problem has gone for good.

    That said, the default lakehouse has not changed as far as I'm aware, so if this turns out to be the solution, then the root cause may be something else.

    BR,

    Søren 

  • Anonymous's avatar
    Anonymous
    Not applicable
    1 year ago

    I have the exact same problem and can't use the ABFS path because my notebooks are part of a deployment pipeline that changes the default lakehouse via deployment rule. So I totally rely on the default lakehouse being flexible.