locked
Cannot run python notebook in Jupyter RRS feed

  • Question

  • I deployed Azure Spark HDInsight and install anaconda

    Then try to run a  python notebook in Jupyter, got error:

    The code failed because of a fatal error:

    Failed to register auto viz for notebook.
    Exception details:

    "cannot import name DataError".

    Tried to restart the jupyter kernel or close-reopen notebook but did not fix the problem

    This error is intermittent.  I deleted cluster then recreate again, sometimes work but sometimes cannot, have to try many times.

    Anyone can help how to fix this error?

    Thank you


    Wednesday, May 23, 2018 1:26 AM

All replies

  • In order to investigate your issue:

    Could you share the steps which you are trying, if you are following any document kindly post here? and could you share the complete error message (Traceback (most recent call last))?

    Wednesday, May 23, 2018 4:51 AM
  • Hi,

    I assume you are using sparkmagic as I see your exception in the code here:

    https://github.com/jupyter-incubator/sparkmagic/blob/master/sparkmagic/sparkmagic/kernels/wrapperkernel/sparkkernelbase.py

    It looks like the issue was caused by a change in pandas 0.23.0:

    https://github.com/jupyter-incubator/sparkmagic/issues/458

    It looks like the changes for a fix were committed but there were CI errors that failed the build:

    https://github.com/jupyter-incubator/sparkmagic/pull/459

    You could make the fixes to the code yourself on your local build, or maybe test downgrading the version of pandas your are using to 0.22 as I see the commit comment for the fix "maintain backwards compatability with Pandas 0.22 or lower for DataError".


    Thursday, May 24, 2018 9:55 PM
  • Hi Jason,

    Thanks for your reply.  

    Yes confirmed the problem is caused by panda version 0.23.

    I did another work around, after I deployed the spark cluster, i did not update to ver 0.23 instead I keep using v 0.20, chich is current  built in version in latest spark version.

    And i did not experience the error.

    Thank you for your help.


    Ryan Suryanto


    Saturday, June 23, 2018 7:50 AM
  • Hey Ryan,

    Thanks for updating the forum with the solution that worked for you, which might help other community members.

    Saturday, June 23, 2018 7:56 AM