Release Notes#

December 4, 2024 4:00PM PT - 2024.11.30-7b90c864#

New Features and Enhancements#

• The CDC Engine now autosuspends after thirty minutes of activity and is automatically resumed when changes to a data stream’s source data are detected or a new data stream is created. As part of this change, the CDC engine is now suspended when the CDC service is disabled and resumed (or, if needed, created) when the CDC service is enabled. Previously, the CDC engine was deleted if you disabled the CDC service.
• The timeout for provisioning an engine has been reduced from thirty minutes to twenty minutes.
• Engine names now require a minimum of three characters. If you pass a name with fewer than three characters to the api.create_engine() procedure, you will get the following error: invalid engine name - valid characters are a-z, A-Z, 0-9, and _, name must be between 3 and 50 characters long.

November 27, 2024 4:00PM PT - 2024.11.25-3438f573-2#

New Features and Enhancements#

• Improved error messages in various resource management edge cases, including when the warehouse runs out of capacity and when warehouses are deleted mid-run.
• Improved error messages when a transaction is aborted due to extremely large rule-sets.

Bug Fixes#

• Engine upgrade failures during initialization are now better handled.

Deprecations and Removals#

• The deprecated app.setup_cdc() procedure has been removed. The work that this procedure was responsible for is performed by app.resume_cdc().

November 22, 2024 12:00PM PT - 2024.11.17-087db490-1#

Bug Fixes#

• Fixes an issue that caused an some engines to experience an unrecoverable engine is upgrading error when an engine upgrade failed to initialize.

November 20, 2024 4:00PM PT - 2024.11.17-087db490#

New Features and Enhancements#

• In version 2024114-2a37e311-1, we changed the instance family for the RELATIONAL_AI_ERP_COMPUTE_POOL provisioned by new RAI Native App installs to CPU_X64_XS instead of CPU_X64_S.

  In this release, older apps with CPU_X64_S compute pools will be automatically migrated to CPU_X64_XS. This reduces the number of Snowflake credits consumed by the application without affecting performance.

Bug Fixes#

• Changes to a data stream’s source object’s columns will now result in the stream being quarantined instead of leaving the stream in a broken state. You may resume the quarantined stream to synchronize the schema changes with models built using the RAI Python API.
• A transaction metadata not found error is no longer raised when a transaction is aborted.

Deprecations and Removals#

• The deprecated relationalai.app.finalize_install() procedure has been removed. The work that this procedure was responsible for is performed by app.activate().

November 13, 2024 4:00pm PT - 2024.11.10-4f524894#

New Features and Enhancements#

You can now configure engines to automatically suspend after a period of inactivity:

• The api.create_engine() procedure has a new engine_config parameter that accepts a JSON object, like {'auto_suspend_mins': 60, 'await_storage_vacuum': false}, for configuring how many minutes an engine must be inactive before being suspended and whether or not garbage collection tasks must complete before suspending the engine. If engine_config is NULL, the engine is configured with auto_suspend_mins set to 0, and the engine will not be automatically suspended.

• The default value for auto_suspend_mins will change from 0 to 60 minutes in a future release. To avoid unexpected behavior, we recommend creating engines with an explicit auto_suspend_mins value. Beginning with version 0.6.0 of the RAI Python API, engines auto-created by the API will be configured with auto_suspend_min set to value of the auto_suspend_min configuration key, or 60 minutes if the key is missing.

• An api.alter_engine_auto_suspend_mins() procedure has been added to alter an existing engine’s auto_suspend_mins configuration parameter. Note that this procedure only works for engines created using the new api.create_engine() procedure mentioned above.

• Use the new api.resume_engine() procedure to resume a suspended engine. Beginning with version 0.6.0 of the RAI Python API, suspended engines will be resumed automatically when Python queries are executed.

• The api.engines view, as well as the table returned by api.get_engine(), now include an AUTO_SUSPEND_MINS and AWAIT_STORAGE_VACUUM columns that contain the configured values for each engine. The new SUSPENDS_AT column shows the timestamp of the next scheduled suspension for inactive engines.

Fixes#

• Fixed a bug that periodically resumed the app warehouse while the Native App was deactivated.

December 5, 2024 - 0.6.4#

Bug Fixes#

• Fixes a bug that caused a too many values to unpack error when setting format="snowpark" in a Model.query() context.

December 4, 2024 - 0.6.3#

Bug Fixes#

• Fixes a bug that caused Model.export() to fail.

December 4, 2024 - 0.6.2#

Bug Fixes#

• Fixes a bug that caused a SQL compilation error the first time a Snowflake table or view was used as a source in a model.

December 3, 2024 - 0.6.1#

New Features and Enhancements#

• The save_config() function now returns None instead of a string with the full TOML file contents. This prevents sensitive information from being displayed in notebook and REPL outputs.

• You will now see a warning message when initializing a model if an engine with the same name as the engine configuration key exists but has a different size than the one specified by the engine_size key.

  To silence this warning, you may do one of the following:

  • Remove the engine_size configuration key from your configuration.
  • Change engine_size to match the size of the existing engine.
  • Delete the existing engine and re-run your program.

• The operation for fetching query results from the RAI Native App is now automatically retried on failure due to a transient error.

Bug Fixes#

• The imports:list CLI command now displays the status Not Available instead of throwing an error if an import’s STATUS field is null.

November 15, 2024 - 0.6.0#

This is a breaking change release. See Breaking Changes for details.

New Features and Enhancements#

• Snowflake Notebooks on Container Runtime are now supported! Container Notebooks offer a more flexible environment than Warehouse Notebooks:

  • You can install the relationalai package using pip install relationalai instead of uploading the package as a ZIP file. This requires enabling an external access integration for PyPI, and lets you install other third-party packages, as well. ZIP file uploads are still supported if you do not want to enable external access to PyPI.

  • You do not need to enable external access integration for downloading query results to the notebook, like you do for Warehouse Notebooks.

• Data streams are now automatically created for you on Snowflake tables and views passed to the source parameter of the model.Type() constructor. Existing data streams will be recreated the first time you query a model using 0.6.0. See Migrating Models to 0.6.0 for more information.

• You can set the new ensure_change_tracking configuration key to automatically enable change tracking on tables or views passed to the model.Type() constructor’s source parameter. The default value is False, which means that table and view owners must manually enable change tracking on their objects.

• Engines auto-created by the Python API are configured by default to suspend after 60 minutes of inactivity. You can override this default by specifying the auto_suspend_mins configuration key in your raiconfig.toml file. Suspended engines are automatically resumed when Python queries are executed. See Engine Suspension for more information on suspended engines.

• A convenience function save_config() has been added for creating a raiconfig.toml file from a notebook environment.

• The Graph.visualize() function now throws an UnsupportedVisualizationError if called in an environment, like a Snowflake notebook, that does not support visualization.

Bug Fixes#

• Fixes a bug that caused an UninitializedPropertyException to be thrown when a type that has never been added to is queried.

• Fixes a bug that displayed the message Failed to connect to ws://0.0.0.0:8080/ws/program. Running with debug sink disabled. when the RAI debugger is not running.

Breaking Changes#

• Several methods of the graphs.Compute class have been changed or removed:

  • .is_triangle() no longer returns an Expression object that produces True or False values. Instead, it filters arguments for combinations of three nodes that form a triangle. This behavior is consistent with how other functions, like .is_reachable(), work.

  • .louvain() now throws a DirectedGraphNotApplicable error if called from a directed graph.

  • The default values for the max_levels and max_sweeps parameters of the .louvain() and .infomap() methods have been changed:

    • max_levels has changed from 4 to 1.
    • max_sweeps has changed from 8 to 20.

  • You may now call the following methods from a weighted graph:

    • .cosine_similarity()
    • .degree_centrality()
    • .distance()
    • .jaccard_similarity()

    Previously, these returned empty results for weighted graphs. Because they now support weighted graphs, the following methods have been removed:

    • .weighted_cosine_similarity()
    • .weighted_degree_centrality()
    • .weighted_distance()
    • .weighted_jaccard_similarity()

  • Methods for computing degree statistics have been removed:

    • .avg_degree()
    • .avg_indegree()
    • .avg_outdegree()
    • .max_degree()
    • .max_indegree()
    • .max_outdegree()
    • .min_degree()
    • .min_indegree()
    • .min_outdegree()

    You can compute these statistics using the .degree() method and an aggregation function:

    #from relationalai.std import aggregates
    
    def avg_degree(graph):
        node = graph.Node()
        degree = graph.compute.degree(node)
        return aggregates.avg(degree)
    

• Internal node hashes for graphs are now stable. Algorithms sensitive to node order will now produce consistent results across different runs.

• All output fields for the rai imports:setup CLI command are now displayed in snake_case. Previously, some were displayed in camelCase while others were displayed in snake_case.

• The --pool parameter for the rai engines:create CLI command has been removed. Engine compute pools are fully managed by the RAI Native App.

Migrating Models to 0.6.0#

The first time you query an existing model after upgrading to 0.6.0, data streams used by the model will be recreated. New data streams appear in the api.data_streams view with a RAI_DATABASE column containing the name pyrel_root_db.

Once the new data streams are created, you can safely delete the old data streams using the api.delete_data_stream() procedure by passing your model’s name and the fully-qualified name of the table or view associated with the old data stream.

#CALL relationalai.api.delete_data_stream('my_model', '<db>.<schema>.<table_or_view>');