Release Notes
For Self-Hosted deployments
These are the relevant changes that are introduced in each specific self-hosted release version.
If you're looking for the latest features and updates in the platform, please visit the What's new section, where you'll also find more details about each feature.
New:
- Workflows: Automate data preparation & analysis pipelines with our no-code workflow design tool. Exporting in Workflows is disabled by default in Self-Hosted instances.
- SQL Parameters in Builder: SQL Parameters are placeholders that can be used on any SQL Query data source in Builder. Once defined, the actual value for the parameter can be set through a control UI, allowing easy manipulation of the data source by both Editor and Viewer users.
- New API Access Tokens UI: developers now have an easy way to create and manage their API Access Tokens, used for authentication in CARTO for Developers.
- Table optimizations: CARTO will now detect automatically whenever a table could perform better thanks to geospatial optimizations, that can be applied from Data Explorer.
- Labels for tile layers: CARTO Builder now supports adding labels to point layers loaded via tiles, with a set of improved features.
- Default role for new users: admins can now select what is the default role for every new user that signs up to their organization.
- Just-in-time provisioning in SSO organizations: admins that have previously set up an SSO integration now have the ability to let their users skip all the onboarding steps, for a seamless signup experience.
- Accessing the CARTO Data Warehouse SQL console: we have enabled an easy way of getting authorization (via a Google account) to the console of their CARTO Data Warehouse.
- Beta Support in Maps API for raster sources created via Beta functions in Analytics Toolbox for BigQuery.
Improvements:
- Refresh buttons have been added in several places when listing and previewing data, to prevent cache issues.
- We’ve added additional optional parameters in Imports API to support upcoming features.
- We’ve made available a private Beta Version of a new feature: Basemap selector for public maps. Please contact the team if you’re interested.
- Be able to disable TrackJS for www components
- Add support for PodDisruptionBudget (disabled by default). A PDB limits the number of Pods of a replicated application that are down simultaneously from voluntary disruptions
- Disable upstream buffering in the router component for APIs that uses streaming to transfer data to the client. We disabled it for the self-hosted behavior to be aligned with the SaaS.
- Other minor changes and improvements
Fixes from the last release:
- Fixed potential issues where containers would not shutdown correctly after receiving SIGTERM signal by:
- Start docker containers in Exec form. So the process will take up PID 1 inside the container and Kubernetes will be able to send signals to the pod.
- Add terminationGracePeriodSeconds to all pods. Now, Kubernetes will wait for a specified time called the termination grace period before killing the containers when it needs to stop them, so the APIs will be able to finish their work before shutdown in a correct way.
- Fixed an issue that would make embedded maps not work outside of the self-hosted domain. Now the router component returns the header X-Frame-Options = “ALLOW” for public map requests.
- Fixed an issue when sending requests to SQL API larger than 1 Mb. Now you can send requests up to 10Mb of payload.
- Fixed an issue while trying to download helm customer packages using the
carto-selfhosted-download.shtool - Fixed a logout problem where users with SSO would be stuck in a logout-login loop under specific circumstances.
- Fixed minor issues with GEOMETRY type handling in Redshift.
- Fixed an issue where the COUNT operation wouldn’t be available for Quadbin layers in Builder.
- Fixed an issue where the dynamic aggregation of points into Quadbin wouldn’t work for Snowflake and PostgreSQL connections under specific circumstances in Builder.
- Fixed an issue where widgets would not be accurate with tileset data sources under specific circumstances.
- Other minor fixes
New:
- New Usage Quota and new LDS quota system: There’s a new API-based usage quota, the LDS quota is now annual and combined, plus other quota-related changes. This feature brings a new component named
router-metricsthat will send aggregated and anonymized API usage metrics periodically. - New Builder SQL Analysis in Redshift and Snowflake: A set of new analyses have been added to Builder, to reach the same level of support on different data warehouse
- Support for imports in Redshift: the feature has been released to General Availability, with no meaningful changes for self-hosted deployments, that will still be required to setup an AWS S3 bucket.
- New environment variable to disable TrackJS: TrackJS is a service used by CARTO for JavaScript error logging. It is now optional for self-hosted deployments.
Improvements:
- The appearance of some screens in the login/signup contexts have changed to match our design system.
- Import API and LDS API can now be selected and used as
allowed_apisin tokens created via Tokens API. - Performance improvements related to the ability to cancel queries and manage timeouts for unused tiles in maps.
- Removed support for fixed radius (meters) in Builder.
- Several performance improvements for Snowflake connections, including better handling of a connection pool for Maps API and SQL API and faster queries for point-based data sources.
- Database parameter is now mandatory when creating Snowflake connections.
- Several improvements when importing files:
- Longer timeout for importing larger files (from 10 minutes to 1 hour)
- Better error handling, with improved error tolerance and clearer error messages.
- The resulting tables in Snowflake after importing are now correctly optimized.
- Other minor changes and improvements
Fixes from the last release:
- Fixed an issue where users could attempt to delete maps owned by a different user.
- Fixed an issue where invitations could be duplicated due to case sensitivity.
- Fixed an issue with Builder SQL console where the spatial data type would remain cached.
- Fixed an issue where an OAuth connection could be marked as shared under specific circumstances.
- Fixed an issue with quantiles calculation not being consistent in static tilesets versus dynamic tiling.
- Fixed several issues with the map/connection sharing dialog, where it would not behave correctly under some circumstances.
- Fixed an issue where a demo dataset for retail industry use cases would appear to non-retail industry users.
- Fixed an issue with the generation of “Intersect an Aggregate” SQL Analysis for Redshift in Builder.
- Fixed an issue to support resolution levels lower than 4 for H3 layers and lower than 6 for Quadbin layers in Builder.
- Other minor fixes
The release notes for releases prior to 2023.3.31 can be found:
Last modified 2h ago