What's New
Major features and updates plus known issues for Cloudera Data Science Workbench 1.9.0.
New features
- ML Runtimes - As an alternative to the existing Engines in CML, ML Runtimes are more lightweight than the current monolithic Engines. By specifying the desired Editor, Kernel, Edition, and Version, a streamlined Runtime will be used to run the user’s code in Sessions, Jobs, Experiments, Models, or Applications.
- Support for ML Ops Governance - MLOps Governance is now supported on CDP Private Base.
- Updated Data Science Project dashboard - The Data Scientist Project dashboard has been updated.
- LDAP Group Sync - You can now create a team that synchronizes with an LDAP group to more easily manage user access to a team.
- Support for applications with public, unauthenticated access - Applications can now be configured for public, unauthenticated access.
- Support for SLES12 SP5, CentOS/RHEL 7.8 - SLES12 SP5, CentOS/RHEL 7.8 are now supported operating systems.
- ML Runtimes supports JupyterLab (Technical Preview) - JupyterLab is now an available ML Runtime, in technical preview.
- Documentation new look and feel -
- Navigation Bar - Subjects are now grouped under major categories.
You'll notice that we've added some major categories and grouped subjects under these categories. For example, there are now Concept, Installation & Upgrade, and How To categories among others. Relevant subjects are grouped under these categories. Under Concepts you'll find Overview and Architecture information. Under How To, you'll find the Quick Start and User Guides, along with information on how to set up and configure Projects, Editors, Model, etc.
- Introduction of foyer pages
Foyer pages provide additional information about the topics grouped under that subject. Foyer pages are only used for subjects that contain a lot of major topics. For example, Site Administration provides a foyer page that lists and defines the major subjects contained in Site Administration, including Monitoring, Quotas, and Data Collection.
- New links are necessary
As part of restructuring the documentation, we separated many large topics into smaller, more concise topics. As a result, topic titles have changed and any links you've saved to previous CDSW releases will not work for CDSW 1.9.0.
- Navigation Bar - Subjects are now grouped under major categories.
Fixed issues
-
The issue with Restart is now fixed.
If multiple users clicked Restart multiple times around the same time, it was possible to have multiple engines running per applications. This resulted in a round-robin like behavior.
Also, in this situation, if a user stopped the application, even though the application said it stopped, the application was still serving on the provided subdomain, because of the zombie engines created in the process above.
Cloudera Bug: DSE-12732
- Cloudera Data Science Workbench Administrator can now
view all projects on Projects page.
Cloudera Bug: DSE-12057
- You can now start, stop, and delete applications stuck in a stopped state after
upgrading to CDSW 1.8.0.
Cloudera Bug: DSE-12374
- The Export Session List option on
the Administration/Usage page now generates a list that is sortable
by date. The Created At column displays a date value that can be
used for sorting.
Cloudera Bug: DSE-9661
- The Export PDF function is improved and will display
charts, tables, and maps. However, some content still might not display well, such as
tables with many columns and dynamic content, video, or iframe content containing dynamic
content.
Cloudera Bug: DSE-11685
- Models and Applications can now use Cloudera Manager and
CDSW proxy settings properly. This issue also caused problems building certain Models and
Applications and requring proxy settings to install additional packages (for example,
pip). This issue is also fixed.
Cloudera Bug: DSE-5467
- Previously CDSW hosts required that IPv6 support was
enabled. This issue is now fixed. CDSW will function with IPv6 networking disabled or
without IPv6 kernel support.
Cloudera Bug: DSE-13465
For a list of supported CDSW versions, see Support Lifecycle Policy