Notebook Workspaces - The JupyterLab integration has been expanded and generalized into Notebook Workspaces. Previously, the JupyterLab menu item provided each user with their own, single JupyterLab workspace. Now users can create multiple Notebook Workspaces that can be shared with other users.
Unifying Syntasa Notebook Cards and JupyterLab - Initial steps are underway to unify these notebook features. Within 9.0.0, a user’s notebook cards will be visible within the user's default Notebook Workspace.
Jupyter AI - JupyterLab notebook feature within the Syntasa application has been integrated with Jupyter AI. The feature can be configured to use models like Bedrock that are available in secure networks.
Notebook Process - Notebooks, i.e., Syntasa notebook cards and JupyterLab notebooks, can be included within Syntasa apps via notebook process nodes. These can therefore be included in jobs and scheduled for recurring execution.
Runtime and Job Execution Improvements
Geospatial Support Enhancements - Runtimes and notebook kernels have been improved to natively support geospatial libraries GeoMesa, Sedona, and H3 Spark. This geospatial configuration is no longer required to be set up within the runtime. With this enhancement, when executing Scala and Python code in a notebook, users can now select any runtime, and the code will execute correctly without any special runtime configurations.
Job Concurrency Management - Configuration options are now available to increase the number of jobs that can be run in parallel up to 50.
Runtime Management - The Runtime Management screen has been enhanced to include a Stop button to terminate running runtimes.
Platform updates
Register Datasets - Eliminating the need for ingestion, external datasets can be registered into a Syntasa datastore. The external datasets can be connected to processes and utilized within Syntasa apps.
Superset Upgrade - Superset, the embedded visualization tool, has been upgraded to version 5.0. - Superset 5.0 Release Notes
Further Git Integration - In addition to the previously introduced primary Git repository, defined within the Infrastructure screen, secondary Git repositories can be added via a new connection type, Git Repo. The secondary Git repositories can be used to import/create new apps from app exports generated in other Syntasa environments and stored in a Git repository.
Object Sharing Options Default - The sharing option seen on many objects throughout the Syntasa application, i.e., Private, Group, and Public, is now, by default, set to Private instead of Public, but the default value is configurable at the system level.