What's New in Version 2024.12.16-9486a276

New Features and Enhancements

You may now optionally specify which underlying RAI Native App resources are dropped when you call the app.deactivate() procedure. For example, the following deactivates the app and drops the app’s warehouse:
```
CALL relationalai.app.deactivate('warehouse')
```
Supported options are:
- 'all'
- 'warehouse'
- 'compute_pool'
- 'service'
The default value is NULL, which means no resources are dropped. This is consistent with the behavior of app.deactivate() prior to this release.
The STATUS column in the api.engines view and the table returned by the api.get_engine() procedure now shows the status UPGRADING if an engine is currently being upgraded.
Query performance on engines that are resumed after having been suspended has been slightly improved.

The api.engines view no longer returns a row for an engine named compcache. The compcache resource may not be used as an engine and is reserved for internal use by the RAI Native App.
When an engine compute pool is at capacity and you attempt to create an engine with an existing name, you will now see an engine already exists error instead of a compute pool at capacity error.
Fixed a bug that occasionally caused the app.activate() procedure to fail due to attempting to communicate with the RAI SPCS Service before it was available.

Fixed a bug that caused some users to see the following error:

Object 'RELATIONALAI.APP_STATE.RAI_DATABASE_SOURCES' does not exist or not authorized.