Version:

Profiles 0.17.x Changelog

Changelog for Profiles v0.17.x.

  •   2 minute read  

  • Last modified: Aug 14, 2024

Version 0.17

14 August 2024
Schema version: 72

What’s New

  • pb show plan: A new subcommand is added to show detailed information about the materials with different timegrains along with their dependencies in the order of execution.
  • The casing for the input tables names defined using double quotes is preserved in the warehouse. For example, the table defined as table: "TableName" will be referred as TableName in the warehouse.
  • Schema has been updated from 71 to 72.

Improvements

  • Relevant error message is shown if the computed status for a material is not possible.
  • An error is thrown if multiple feature views are defined with the same name.

Bug Fixes

  • Fixed the issue where input_vars was not getting defined on the packages.
  • Resolved the bug where the project was failing due to empty or commented YAML files.

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.
  • The code for validity_time is redundant and should be removed.
  • Timegrains is an experimental feature. There might be some undiscovered issues.

Questions? Contact us by email or on Slack