You are viewing documentation for an older version.

Click here to view the latest documentation.

Version 0.20.3

3 February 2025

Bug Fixes

• Fixed a performance issue for nested column models by adding LIMIT 1 to the query that checks if a column exists or not.

Version 0.20.2

28 January 2025

Bug Fixes

• Fixed an issue where project fails on Snowflake and Redshift when the ID columns are of non-string types.

Version 0.20.1

27 January 2025

Bug Fixes

• Fixed an issue wherein any changes to id_types are not considered in the ID stitcher model hash computation.

Version 0.20

21 January 2025
Schema version: 85

Release Schedule

• CLI: January 21, 2025
• Deployment to dev workspaces: January 21, 2025
• Deployment to prod workspaces: January 25, 2025

What’s New

• Schema has been updated from 84 to 85.
• Added a column description: The YAML description of each feature now gets added in feature_views as a comment in the corresponding column.
• Azure DevOps Git URLs are now supported while creating the Profiles project in the dashboard. See Import Profiles Project from Git for more information.
• WHERE clause support: Input YAMLs now support the WHERE clause, helping you filter out any unnecessary rows from the source and reduce the need for an additional SQL model.
• A new command pb tutorial is now added. Profiles Tutorial is a guided interactive tutorial within the Profiles CLI and walks you through the key Profiles concepts and how they work. See Profiles Tutorial for more information.

Improvements

• ID stitcher performance improvements: Rows in the ID stitcher table are compacted based on node_id, node_id_type, and main_id to remove duplicates. Also, some unnecessary steps are removed from the ID stitching process to make it faster.
• Removed empty lines from the generated SQL to make it more readable.
• The SQL errors now show the file path and the corresponding error, instead of printing the entire query in the console/logs.
• Removed some unnecessary internal models to simplify the model graph in case of column models.

Bug Fixes

• Fixed the issue wherein running the var materials failed sometimes if the PB process was killed forcefully, by making the process idempotent.
• You can now refer to features on SQL models and Python model (non-entity-var features) also using the general path reference for the feature, i.e. <entity>/<cohort>/<feature-name>. You can also refer to the inherited features in the same way.
• Fixed the issue wherein --output_folder flag was not respected in pb run and pb compile commands by supporting absolute paths.

Deprecation

• python_model model type is now deprecated.

Known Issues

BigQuery

• pb validate access command does not work for BigQuery.

Redshift

• If two different users create material objects on the same schema, RudderStack gives an error during cleanup when trying to drop views created by the other user, like user_var_table.
• Cross database references can fail on Redshift for a few clusters.
• While creating Activations, validation for Redshift does not work correctly in the RudderStack dashboard.

Other issues

• Linux users might see this warning for all command runs - you can ignore it: WARN[0000]log.go:228 gosnowflake.(*defaultLogger).Warn DBUS_SESSION_BUS_ADDRESS envvar looks to be not set, this can lead to runaway dbus-daemon processes. To avoid this, set envvar DBUS_SESSION_BUS_ADDRESS=$XDG_RUNTIME_DIR/bus (if it exists) or DBUS_SESSION_BUS_ADDRESS=/dev/null.
• pb insert does not work for Redshift, Databricks, and BigQuery.
• If you are referring a public package in the project and get ssh: handshake failed error, then you’ll have to manually remove the entire folder from WhtGitCache to make it work.
• Timegrains is an experimental feature. There might be some undiscovered issues.