You are viewing documentation for an older version.
Profiles 0.19.x Changelog
3 minute read
- Last modified: Aug 7, 2026
Version 0.19.3
9 January 2025
Bug Fixes
- Properly sets the Snowflake connection parameter
applicationtoRudderstack_Warehouse.
Version 0.19.2
6 December 2024
Bug Fixes
- Fixed a common tables migration bug where PB may go into an unrecoverable state when you run it in two parallel processes.
- Fixed an inconsistency in incremental ID stitching due to differences in how warehouses treat NULL values sorting.
- Fixed a bug in incremental ID stitching related to occasional changes in the main IDs when you add new edges to the cluster.
Version 0.19.1
29 November 2024
Bug Fixes
- Fixed a bug causing an unexpected change in the profiles ID when the ID stitcher is running in incremental mode..
- Fixed a crash that occurs while parsing a YAML which starts with a list at the root level.
Version 0.19
14 November 2024
Schema version: 84
What’s New
- Schema has been updated from 80 to 84.
- Project created using
pb init pb-projectnow locks the PB version. - Task summary is now shown at the end of each run, including relevant command details like start time, end time, sequence number, and total models processed (if any).
- The number of iterations/loops during ID stitching are now logged.
- A new tool named Profiles ID Stitcher Audit tool is introduced. It is embedded within the core PB CLI tool and helps you analyze the health of your ID graph by giving you a high level aggregate analysis of your ID graph across entities. You can also analyze a single cluster by visualizing all IDs and their connections, along with highlighting the most important IDs that form connections in that group.
- A key named
carry_forward_privileges(type Boolean) is added in thepb_project.yamlfile. This key determines whether the privileges granted on the views should be retained after the view definitions are updated. This resolves the issue where recreating views for each model in the project led to revoked privileges. Note that using this key can lead to some performance overhead. - A new column named
pb_versionis added to thematerial_registrytable in the database which denotes the PB version that created the entry. - A new flag
pb show idstitcher-report --seed_clusters_csvis added which you can use to pass a CSV file with two columns -idandid_type. The cluster ID can be eitherrudder_idorother_id. Each row specifies an ID to be mapped to a cluster main ID, which is then included in the report.
Improvements
- An error is now thrown if a model has a feature without any IDs.
- User-friendly messages are shown in case a package isn’t installed.
- Error is now thrown if duplicate feature names are present for a cohort.
Bug fixes
- Resolved the cleanup issue where some materials cleanup failed due to dependencies.
- Fixed an issue where a non-existent folder inside
model_folderscaused the project to fail.
Known Issues
BigQuery
pb validate accesscommand 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 insertdoes 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 fromWhtGitCacheto make it work. - Timegrains is an experimental feature. There might be some undiscovered issues.