Version 0.9.5 of the RelationalAI Python API is now available with bug fixes for users who use RAI in Snowflake Notebooks.
To upgrade, activate your virtual environment and run the following command:
pip install --upgrade relationalaiType.define() method to fail in Snowflake Notebooks with the error Exception: Can't iterate over a producer.
This release introduces a new show_full_traces configuration option that can be used to enable full error stack traces in the Python client for an improved debugging experience.
To upgrade, activate your virtual environment and run the following command:
pip install --upgrade relationalaiYou can now enable full error stack traces by setting the new show_full_traces configuration option to True.
This helps with debugging by showing complete exception details when errors occur.
By default, show_full_traces is False, so error messages remain concise for a cleaner user experience. To see full traces, set this option programmatically or via your config file:
Add the following to your config file:
active_profile = "default"show_full_traces = true
[profile.default]user = "<MY_SNOWFLAKE_USER>"password = "<MY_SNOWFLAKE_PASSWORD>"account = "<MY_SNOWFLAKE_ACCOUNT>"role = "<MY_SNOWFLAKE_ROLE>"warehouse = "<MY_SNOWFLAKE_WAREHOUSE>"import relationalai as rai
cfg = rai.Config({ "user": "<MY_SNOWFLAKE_USER>", "password": "<MY_SNOWFLAKE_PASSWORD>", "account": "<MY_SNOWFLAKE_ACCOUNT>", "role": "<MY_SNOWFLAKE_ROLE>", "warehouse": "<MY_SNOWFLAKE_WAREHOUSE>", "show_full_traces": True})
model = rai.Model("MyModel", config=cfg)
This release fixes a bug in the .full_reachable_from() graph method and improves error messages for missing data streams.
To upgrade, activate your virtual environment and run the following command:
pip install --upgrade relationalai.full_reachable_from() graph method that caused some graph queries to fail or return incorrect results.
This release makes our new, faster storage format the default for all new RAI Native App installations.
RelationalAI Native App upgrades are applied automatically and require no action on your part, unless you have opted-in to manual upgrades.
In last week’s release, we introduced a new internal data format that significantly improves query performance, especially on cold engines. This week’s release makes this new storage format the default for all new RAI Native App installations.
This release includes a bug fix for engine initialization states.
Note that RelationalAI Native App upgrades are applied automatically and require no action on your part, unless you have opted-in to manual upgrades.
Fixed an issue that caused some engines to report a READY state when they were not fully initialized, which led to errors like the following:
engine is provisioning - please retry the transaction later
This release includes important performance improvements and enhancements to the Snowflake native app installation process and internal storage cleanup reliability.
Note that RelationalAI Native App upgrades are applied automatically and require no action on your part, unless you have disabled automatic upgrades. One exception this week is a manual migration step required to take advantage of new performance improvements.
We’ve migrated the RAI Native App to a new internal data format that significantly improves query performance! The new data format will allow us to dramatically reduce the compilation time, also called warmup time, that our logic engines require to process queries.
Benefits include:
Beginning with the next release, all new installations will use this new format. We’re asking all existing users to manually migrate their app to this new format to take advantage of these performance improvements. See the Migration Guide for step-by-step instructions.
The RAI Native App now uses Snowflake Manifest Version 2, which enables automatic privilege management. All Snowflake privileges required by the app are granted automatically during installation, so manual grants are no longer needed.
Existing installations already have the necessary privileges, so no action is needed for current users. This change mainly affects new installations.
Note that after this change, the privileges granted to the app cannot be revoked, even if you installed the app before this release. See the Installation guide for more details.
We recommend performing the migration during a maintenance window or when your app is not in active use.
During the migration:
To migrate your app to the new data format:
First, delete any old or unused CDC streams that do not need to be migrated. This will reduce the amount of data that needs to be migrated and speed up the process. See Delete a Data Stream for instructions.
Next, execute the following SQL as an app admin (or ACCOUNTADMIN) to begin the migration:
CALL relationalai.api.upgrade_storage_format_with_downtime('1');This will block for a few minutes while the app is taken offline and the migration steps are prepared. When it returns, the migration steps will be completed, and the CDC rebuilding process will have begun.
Use the following SQL to poll for CDC rebuilding status:
CALL relationalai.api.show_storage_upgrade_status();You can resume your ordinary workloads at any time during CDC rebuilding, and they will simply block until the data is loaded, per normal RAI data stream behavior.
Note that running the migration on an already migrated account will produce an error message and is otherwise a noop.