Notebooks and Dashboards

Jupyter Notebooks (Beta)

New Feature

  • JUPY-193: You can now create and manage Jupyter notebooks using REST APIs.

Enhancements

  • JUPY-272: You can now use the QDS Object Storage Explorer on the left sidebar of the JupyterLab UI to explore Cloud storage, and to perform actions such as uploading or downloading a file.
  • JUPY-271: You can now use the Table Explorer from the left sidebar to explore the Hive metastore, schema, tables, and columns.

Bug Fixes

  • JUPY-308: Spark application startup failed in a few cases when third party JARs were added to the Spark configuration. This issue is fixed.

Zeppelin Notebooks

New Features

  • ZEP-493: Bitbucket is now integrated with Notebooks. You can use Bitbucket to manage versions of your notebooks. Learn more.

Enhancements

  • ZEP-3915: Zeppelin 0.8.0 includes he following enhancements:

    • ZEP-2749: Pyspark and IPyspark interpreters are now supported with IPython as the default shell. To set the Python shell as the default for the Pyspark interpreter, set zeppelin.pyspark.useIPython to false in the Interpreter settings. Via Support.
    • ZEP-4077: Notebooks now support z.run(noteId, paragraphId) and z.runNote(noteId) functions to run paragraphs or notebooks from within the notebook.
    • ZEP-3317: You can now run Markdown (%md) paragraphs in edit mode even when the cluster is down.
    • ZEP-1908: The geolocation graph type is now available in the UI by default.
  • ZEP-4129: To optimize memory usage for homogeneous Spark clusters running version 2.3.2 and later, Spark driver memory is now allocated on the basis of the instance type of the cluster worker nodes. Because of this, when configuring a cluster to attach to a notebook, you should not specify the spark.driver.memory property in the Spark cluster overrides (Override Spark Configuration under the Advanced tab). A homogeneous cluster is one in which all the worker nodes are of the same instance type.

  • ZEP-4169 and ZEP-134: The Zeppelin application and all interpreters started by Zeppelin (including Spark and shell interpreters) can now be run under a YARN user. Before this release, Zeppelin applications and interpreters ran as root, a security concern for many enterprises. Via Support.

Bug Fixes

  • ZEP-3298: In case of failure, scheduled notebooks that had retry no.option set in the Scheduler properties were not re-run. This issue is fixed.
  • ZEP-4193: Autocomplete now works for PySpark notebooks in Zeppelin 0.8.0.
  • ZEP-4194: Notebook results were not displayed when clusters running Zeppelin 0.6.0 were upgraded to Zeppelin 0.8.0 or when clusters running Zeppelin 0.8.0 were downgraded to Zeppelin 0.6.0. This issue is fixed.
  • ZEP-3122: The stacked option for graphs and charts in Zeppelin notebooks did not persist after a refresh. This issue is fixed.
  • ZEP-4198: The Notebooks home page was displayed when the cluster was started. This issue is fixed.
  • ZEP-3129: External web links referenced in a Markdown paragraph now open in a separate tab.
  • ZEP-4195 and ZEP-4199: Notebook content was not rendered correctly when a notebook was switched to a different cluster. This issue is fixed.
  • ZEP-4181: The published at field in the Dashboard information on the Notebooks page displayed an incorrect timestamp. This issue is fixed.
  • ZEP-3562: With a large cardinality in multibar charts, a notebook becomes unresponsive. This fix sets a limit of 50 on cardinality. To increase the limit, contact Qubole Support.