[2024/06/14] Query Router Improvements, API Pause for Custom APIs and More!
Welcome to our latest update! We are committed to continuously improving ZettaBlock to enhance your development experience.
Below, you’ll find details on new features and updates:
Query Router Improvements
To improve the reliability and user experience of our query editor, we’ve upgraded the Query Router.
Now, before executing any query, the router verifies the existence of all referenced tables or views in the target database (either PostgreSQL or Data Lake). If a referenced element does not exist, an error is immediately returned through the UI. This update ensures more accurate query execution and reduces the risk of runtime errors.
API Pause for Custom APIs
To help you save on Compute Units (CUs), we are introducing an automatic pause feature for custom APIs. If a custom API has not been called for the past 7 days, the background refresh will be paused. This change can lead to significant savings for your unused APIs.
If you decide you’d like to unpause the API, simply call it again (there are no buttons in the UI). The first call will display stale data - once we detect you are still using the API, we will start refreshing its data again. However, it may take up to 1 hour (plus the refresh interval) for the API to become fully up-to-date. After this period, subsequent calls will show fully refreshed data.
The API list in your workspace will show the paused/ready state and their last refreshed time for all APIs.
Archiving 2 Chains: Base & Avalanche
Starting from June 14th, we will be archiving data for the Base and Avalanche chains. This step is part of our ongoing effort to streamline our platform and ensure optimal performance. Please plan accordingly and reach out if you have any questions or need assistance with this transition.
For support or any questions, please reach out to us on Discord.
Thank you for being a valued member of the ZettaBlock community!