You are viewing documentation for an older version.
Click here to view the latest documentation.

Profiles 0.14.x Changelog

Changelog for Profiles v0.14.x.

Version 0.14.2

28 June 2024

Bug Fixes

26 June 2024

Bug Fixes

19 June 2024 Schema version: 67

What’s New

You can now refer to entity_vars defined on cohorts using the <cohort_name>.Var("<var_name>") syntax along with the original entity.Var("v1") syntax.
Vars from ancestor vars are now inherited in derived cohorts. If a derived cohort has vars with the same name as ancestors, they are overridden.
You can also specify timegrains on a specific entity_var and not only on the entire var_group.
If a column is specified as mandatory in a model contract, it must be present in the warehouse. Otherwise, the project will fail. Also, contract validation is now enabled for SQL models and Python models.
pb show models command now displays additional information such as the enable_status of models, warehouse name, namespace, and timegrains.
In materialization status, the flag not_needed has been renamed to only_if_necessary.
Some experimental features are added to optimize performance by partitioning var tables.
A new key row_identifier (experimental) has been added under app_defaults in the inputs.yaml file.
Schema has been updated from 63 -> 67 in the pb_project.yaml file.

Improvements

Bug Fixes

Fixed the issue where features list wasn’t getting added to input models build specification.
Resolved a bug where <entity>/feature_views model wasn’t getting created, in case the feature_views key didn’t have any value.
Resolved the error where some BigQuery projects were failing with the message Dataset <> not found in location.
Fixed the symlink issue where the pb run/pb compile commands were failing when the relative path of the project is passed.
Resolved the bug where input models were getting enabled if they did not exist earlier, even if their status wasn’t set.
Error is now being thrown in case all the inputs of a model are disabled but they are mandatory.
Fixed the error nil pointer dereference when other_id is not defined in the feature views.
Resolved the issue where different cohorts with same feature names were throwing an error.
Fixed the bug where a derived cohort was not able to refer other cohort’s vars.
Fixed column name is ambiguous error in feature views when there are vars with the same name in different timegrains.
Resolved the issue where some projects with concurrency were failing with error concurrent map read and map write.
Fixed the issue with force runs on models with begin time.

Known Issues

RudderStack does not support accessing input sources in a different project for the BigQuery warehouse.
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.
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.
pb validate access command does not work for BigQuery.
pb insert does not work for Redshift, Databricks, and BigQuery.
Cross database references can fail on Redshift for a few clusters.
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.
The code for validity_time is redundant and should be removed.
In some cases, you may need to install the profiles-rudderstack and profiles-rudderstack-bin pip packages separately.
You may have to execute the compile command once before executing validate access. Otherwise, you will get a seq_no error.
Timegrains is an experimental feature. There might be some undiscovered issues.
Activations does not work with Redshift warehouse.