Version 0.9.18 of the relationalai Python package is now available!
To upgrade, activate your virtual environment and run the following command:
pip install --upgrade relationalai
Version 0.9.17 of the relationalai Python package is now available.
This release includes enhanced engine provisioning error messages and improved Snowflake JWT (Javascript Web Token) authentication for better security and reliability.
To upgrade, activate your virtual environment and run the following command:
pip install --upgrade relationalaiEngineAutoCreateFailed exception has been replaced with EngineProvisioningFailed, which surfaces the original error details for clearer diagnostics during engine provisioning failures.Engine provisioning errors now include the original underlying cause to help you troubleshoot more effectively. When engine creation fails—due to issues like connection timeouts or service problems—the error message will display the specific reason alongside guidance on manual engine management.
Improved security and reliability for Snowflake key-pair JWT authentication in the Python client:
Version 0.9.16 of the relationalai Python package is now available.
This release includes the ability to skip invalid rows during data export or query with detailed warnings to improve transparency and troubleshooting.
To upgrade, activate your virtual environment and run the following command:
pip install --upgrade relationalaiYou can now skip invalid rows during data export or query by using the new skip_invalid_data=True option in the Python API’s query and export methods. When enabled, any rows with invalid data (such as type mismatches or constraint violations) are automatically skipped instead of causing failures.
Importantly, the system will provide detailed warnings showing which rows were rejected, which columns caused errors, and the specific error messages. This helps you quickly identify and fix data quality issues without silent failures or guesswork.
Example Usage:
# Skip invalid data during export@model.export("<my_db>.<my_schema>", skip_invalid_data=True)def my_export(): ...
# Skip invalid data during query:with model.query(skip_invalid_data=True) as select: ...Example warning output:
Your data has been loaded but 2 rows were skipped due to erroneous data. Here are the first 2 rejected rows:Rejected record: {"id": "abc", "amount": "not_a_number"}- Erroneous column: amount Error message: Could not convert value to numeric
Rejected record: {"id": 123, "amount": null}- Erroneous column: amount Error message: Null value not allowed
Version 2025.11.2-6a8205c of the RelationalAI Native App is now available!
Note that RelationalAI Native App upgrades are applied automatically and require no action on your part, unless you have opted-in to manual upgrades.
Version 2025.10.27-1e82ecf-1 of the RelationalAI Native App is now available!
Note that RelationalAI Native App upgrades are applied automatically and require no action on your part, unless you have opted-in to manual upgrades.
User-initiated transactions now have a default timeout of 24 hours (1,440 minutes).
Currently there is no way to change this timeout globally, but Python API users can adjust it for their models by specifying the query_timeout_mins parameter in their raiconfig.toml file.
See Changing the Query Timeout for more information about setting this parameter.
This breaking change improves resource management by preventing long-running transactions from consuming system resources indefinitely.
Version 2025.10.16-9408bf7 of the RAI Native App is now available!
Note that RelationalAI Native App upgrades are applied automatically and require no action on your part, unless you have opted-in to manual upgrades.