Skip to content

Releases: dbt-labs/segment

Segment v0.2.5

25 Feb 18:53
a6914e8
Compare
Choose a tag to compare

Summary

Included in this release:

Segment v0.2.4

19 Dec 20:05
f3835ad
Compare
Choose a tag to compare

This release:

  • Fixes some bad Jinja which (rightfully) throws an error in dbt v0.15.0
  • Introduces Snowflake compatibility
  • Adds integration tests

Segment v0.2.3

01 Apr 19:28
90a71fb
Compare
Choose a tag to compare

New in this release:

  • Added first_seen_at and last_seen_at to segment_web_user_stitching model

Segment v0.2.2

27 Mar 18:37
990e644
Compare
Choose a tag to compare

New in this release:

  • Added mapping for the referrer field to determine referrer_source and referrer_medium

Segment v0.2.1

26 Mar 14:39
dac4099
Compare
Choose a tag to compare

New in this release:

  • Added segment_pass_through_columns variable

Segment v0.2.0

19 Mar 15:24
9de3a09
Compare
Choose a tag to compare

New in this release:

  • fixed bug associated with incorrectly trimming w characters at the beginning of a domain name.
  • added a configurable session inactivity window.

Segment v0.1.7

13 Feb 19:35
d0c9494
Compare
Choose a tag to compare

This is a bugfix release that re-introduces BigQuery compatibility.

Fixes

  • Reverts to using the dbt-utils version date_add instead of the Redshift version (#13)

Segment v0.1.6

06 Feb 22:01
0c0dffd
Compare
Choose a tag to compare

Segment 0.1.6

This is a bugfix release.

Users of this package should upgrade their dbt projects to this release, and run a full-refresh of the models in this package, and any downstream models.

$ dbt run --models segment.*+ --full-refresh

Fixes

  • Fix a bug resulting in incorrect values for web_session.session_number (#11)
  • Make this package compatible with BigQuery (#8)
  • Upgrade to v0.12.2 syntax for incremental models (#7)

Contributors

Segment v0.1.5

25 Jan 15:41
ddf851f
Compare
Choose a tag to compare
  • add device and device_category. Note that this is a breaking change – when upgrading to this version, you will need to perform a full refresh run of your models: dbt run -m segment.*+ --full-refresh

Segment v0.1.4

08 Jan 21:28
2a5a4ea
Compare
Choose a tag to compare
  • Use a package spec for dbt-utils
  • This package now requires the use of dbt v0.12.2 or later