Version:

Profiles 0.21.x Changelog

Changelog for Profiles v0.21.

  •   2 minute read  

  • Last modified: Mar 13, 2025

Version 0.21.4

13 March 2025

Bug Fixes

  • Fixed an issue wherein the metadata of column materials’ parent field was set wrong.
  • Boundaries of month and year timegrains are now made to coincide with week boundary.

Version 0.21.3

11 March 2025

Bug Fixes

  • Fixed Snowflake key-pair auth regression.

Version 0.21.2

6 March 2025
Schema version: 88

Release Schedule

MilestoneDate
CLI releaseMarch 6, 2025
Deployment to dev workspacesMarch 6, 2025
Deployment to production workspacesMarch 11, 2025

What’s New

  • Schema has been updated from 85 to 88.
  • Introduced Timegrains - timegrains give you the ability to control the frequency at which certain models run irrespective of the frequency at which you trigger the Profiles project runs.
  • Introduced a change wherein the IDs to be considered for ID stitching must be of string data type. If ID columns in your inputs are not strings, you must cast them explicitly.

Optimizations

info
These optimizations are still in beta and are released behind feature flags. See Optimizations for more information.
  • Input var bundling: With this optimization, PB automatically bundles the execution of some input_vars together during runtime, based on the var definitions.
  • Entity var bundling: With this optimization, PB automatically bundles the execution of some entity_vars together during runtime, based on the var definitions.

Improvements

  • ID stitcher now runs in incremental mode by default.
  • Reduced the package size by 50% by removing debugging information while building the binary.
  • pb show plan now shows the disabled materials. This is helpful when working with timegrains to understand which materials run in a particular timegrain.

Deprecation

  • Username/password authentication is now deprecated for Snowflake - use key-pair authentication instead.

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.

Questions? Contact us by email or on Slack