You are viewing documentation for an older version.

Click here to view the latest documentation.

Version 0.6.0

26 May 2023

We are excited to announce the release of PB Version 0.6.0: packed with new features, improvements, and enhanced user experience.

What’s New

• Support for begin time and end time: Our latest release introduces the ability to specify time range for your operations, using two new flags --begin_time and --end_time. By default, the --end_time flag is set to now. For example, you can use the command pb run --begin_time 2023-05-01T12:00:00Z to fetch all data loaded after 1st May 2023. Note that the flag --timestamp is now deprecated.
• A new flag, model_refs, has been introduced which restricts the operation to a specified model. You can specify model references, such as pb run --model_refs models/user_id_stitcher.
• seq_no - Another new flag, using which you can Continue a previous run by specifying its sequence number. Models that already exist would not be rebuilt, unless --force is also specified.
• Show command - pb show dependencies has been added to generate a graph showcasing model dependencies. This visual representation will help you understand the relationships between various models in your project.
• Show command - pb show dataflow: Another new command which generates a graph with reversed edges, illustrating the dataflow within your project.
• migrate_on_load - A new flag, migrate_on_load, has been introduced. When executing the command pb run --migrate_on_load, by default this flag creates a migrations folder inside the project folder that has migrated version of your project to the latest schema version and runs it on the warehouse. This simplifies the process of upgrading your project to the latest schema version, without changing source files.
• migrated_folder_path - Continuing from previous command, you can use this flag to change folder location of the migrated project.
• Schema in the project file has been updated to version 33.

Improvements

• SQL Models now provide more relevant and informative error messages instead of generic “not found” errors. This simplifies troubleshooting and debugging processes.
• Numerous improvements and optimizations have been made behind the scenes, enhancing the overall performance and stability of PB.