Releases: dbt-labs/segment
Releases · dbt-labs/segment
Segment v0.2.5
Summary
Included in this release:
- BigQuery compatibility (#37 & #39 @shedd)
- A fix for NULL values (#38 @invinceyble)
Segment v0.2.4
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
New in this release:
- Added
first_seen_at
andlast_seen_at
tosegment_web_user_stitching
model
Segment v0.2.2
New in this release:
- Added mapping for the
referrer
field to determinereferrer_source
andreferrer_medium
Segment v0.2.1
New in this release:
- Added
segment_pass_through_columns
variable
Segment v0.2.0
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
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
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
- add
device
anddevice_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
- Use a package spec for dbt-utils
- This package now requires the use of dbt v0.12.2 or later