Available in June 2024, Syntasa version 7.3.0 adds new functionality and improved stability to the notebook features, introduces a new visualization tool, and many improvements to ease the administration and management of your Syntasa environment.
Superset, a new visualization tool
We're now including a new visualization tool, Superset, within the Dashboards section of Syntasa. This is an additional tool to the existing Helical Insights solution. Dashboards can be created with either of these or any other visualization tool and published within Syntasa for a consolidated set of dashboards easily accessible by users and analysts.
Runtime Management
The new Runtime Management page within the Activity module emerges as a pivotal tool offering insights into the status and history of runtime/cluster instances initiated within the Syntasa ecosystem.
On the page, you can review the current status, uptime, and estimated cost of each runtime/cluster instance. This includes runtimes initiated from app jobs, those started within an app's interactive mode, and those started and attached to a Syntasa notebook.
Notebook enhancements
The Syntasa Notebooks and JupyterLab integration are popular features that continue to be improved with every new version. These improvements continue in Syntasa 7.3.0 with the following updates:
- General stabilization and bug fixes for both Syntasa Notebooks and JupyterLab
- Faster launch for JupterLab notebooks utilizing warm node pools
- Supported languages and language version updates:
- Python 3.10 supported for EMR Syntasa Notebook kernels
- Python 3.10 used in EMR and Spark images
- Removed R language in Syntasa Notebooks
Platform updates
There have also been many fixes, updates, and improvements under the hood, app processes, and job execution usability. The following are the prominent platform updates in this version:
- Spark on Kubernetes support for GCP and AWS installations
- Upgrade to Postgres 14 in all cloud deployments
- The From DB app process now supports Delta format
- For ad-hoc job execution, the Execution Date Range, which differs from the Relative Range for scheduled jobs, can be saved. Previously these fields displayed the most recent job execution values and could be altered at the time of job execution, but couldn't be saved and retained. Now the values can be saved as you wish.
- Azure single sign-on (SSO) is now supported as an authentication method
- Kubernetes Container: Spark Image runtime configuration options - Max Uptime and Idle Time Deletion Interval fields have been added
- AWS installations, in Infrastructure settings the Interactive Engine options updated reference of Presto to Trino