Skip to content

What's New in Version 2026.8.17-c5208f8

August 17, 202610:00 PM UTC

Version 2026.8.17-c5208f8 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.

  • Creating a data stream on a Snowflake-managed Iceberg table now fails immediately with the error Iceberg tables are not supported for CDC data streams. Previously, the stream was created but Snowflake quarantined it, so changes were never processed. See Prepare your data sources for the source objects that data streams support.
  • The new api.cleanup_stale_data_streams() procedure lets you delete data streams that haven’t been accessed for longer than a time-to-live (TTL) you specify. It takes a TTL in minutes and runs in dry-run mode by default, reporting the data streams it would delete without removing anything. Pass DRY_RUN => FALSE to delete them.

  • The api.data_streams view now includes a last_accessed column that shows when each data stream was last accessed by a transaction. The value is NULL for a data stream that has never been accessed.

  • Fixed a rare issue where two internal computations could overwrite each other and affect a query’s results.

  • Writing to a Snowflake-managed Iceberg table no longer fails with an Invalid parquet file: non-nullable column ... has null values according to file statistics error.

  • The app now reconnects to Snowflake on its own when its internal access token expires, so operations like reasoner creation no longer get stuck and fail.

  • Fixed an issue that prevented custom aggregations over decimal values, such as FixedDecimal, from returning results.

  • Prediction jobs submitted by PyRel to a predictive reasoner no longer fail with an index out of range in self error when your data contains a category that wasn’t seen during training.

  • A query that runs while a model’s internal data store is being deleted now reports the accurate error The database does not exist. instead of the misleading Database was closed and this transaction was discarded. Note that “database” here refers to an internal database used by the native app and not a Snowflake database visible in your Snowflake account.