diff --git a/.test/great_expectations/expectations/web/v1/base_redshift.json b/.test/great_expectations/expectations/web/v1/base_redshift.json index 8921a433..64e92cbf 100644 --- a/.test/great_expectations/expectations/web/v1/base_redshift.json +++ b/.test/great_expectations/expectations/web/v1/base_redshift.json @@ -287,7 +287,7 @@ "meta": { "versions": { "test_suite_version": "1.1.1", - "redshift_model_version": "1.3.0" + "redshift_model_version": "1.3.1" }, "great_expectations.__version__": "0.12.0" } diff --git a/.test/great_expectations/expectations/web/v1/metadata.json b/.test/great_expectations/expectations/web/v1/metadata.json index a99b70ef..c088da0e 100644 --- a/.test/great_expectations/expectations/web/v1/metadata.json +++ b/.test/great_expectations/expectations/web/v1/metadata.json @@ -103,7 +103,7 @@ "meta": { "versions": { "test_suite_version": "1.1.1", - "redshift_model_version": "1.3.0", + "redshift_model_version": "1.3.1", "bigquery_model_version": "1.0.3", "snowflake_model_version": "1.0.1" }, diff --git a/.test/great_expectations/expectations/web/v1/page_view_in_session_values.json b/.test/great_expectations/expectations/web/v1/page_view_in_session_values.json index 0e387c02..7122be6b 100644 --- a/.test/great_expectations/expectations/web/v1/page_view_in_session_values.json +++ b/.test/great_expectations/expectations/web/v1/page_view_in_session_values.json @@ -27,7 +27,7 @@ "meta": { "versions": { "test_suite_version": "1.1.1", - "redshift_model_version": "1.3.0", + "redshift_model_version": "1.3.1", "bigquery_model_version": "1.0.3", "snowflake_model_version": "1.0.1" }, diff --git a/.test/great_expectations/expectations/web/v1/page_views.json b/.test/great_expectations/expectations/web/v1/page_views.json index ae30c0c7..78eb439f 100644 --- a/.test/great_expectations/expectations/web/v1/page_views.json +++ b/.test/great_expectations/expectations/web/v1/page_views.json @@ -225,7 +225,7 @@ "meta": { "versions": { "test_suite_version": "1.1.1", - "redshift_model_version": "1.3.0", + "redshift_model_version": "1.3.1", "bigquery_model_version": "1.0.3", "snowflake_model_version": "1.0.1" }, diff --git a/.test/great_expectations/expectations/web/v1/sessions.json b/.test/great_expectations/expectations/web/v1/sessions.json index d652caa5..450ffeaf 100644 --- a/.test/great_expectations/expectations/web/v1/sessions.json +++ b/.test/great_expectations/expectations/web/v1/sessions.json @@ -181,7 +181,7 @@ "meta": { "versions": { "test_suite_version": "1.1.1", - "redshift_model_version": "1.3.0", + "redshift_model_version": "1.3.1", "bigquery_model_version": "1.0.3", "snowflake_model_version": "1.0.1" }, diff --git a/.test/great_expectations/expectations/web/v1/users.json b/.test/great_expectations/expectations/web/v1/users.json index ee6051a1..d090f0d5 100644 --- a/.test/great_expectations/expectations/web/v1/users.json +++ b/.test/great_expectations/expectations/web/v1/users.json @@ -117,7 +117,7 @@ "meta": { "versions": { "test_suite_version": "1.1.1", - "redshift_model_version": "1.3.0", + "redshift_model_version": "1.3.1", "bigquery_model_version": "1.0.3", "snowflake_model_version": "1.0.1" }, diff --git a/CHANGELOG b/CHANGELOG index 6ea0f557..23801e56 100644 --- a/CHANGELOG +++ b/CHANGELOG @@ -1,3 +1,7 @@ +Redshift Web Version 1.3.1 (2022-09-02) +-------------------------------------- +Redshift Web: load_tstamp missing from table definition (#135) + Maintenance release (2022-07-21) -------------------------------- Add migrations for previous releases (#133) diff --git a/README.md b/README.md index 52121dbc..c9870933 100644 --- a/README.md +++ b/README.md @@ -16,7 +16,7 @@ The Snowplow atomic data acts as an immutable log of all the actions that occurr # Try Snowplow -This repo contains data models which are relevant to users who already have a full Snowplow pipeline running (which can be done Open Source or via [Snowplow BDP](https://snowplowanalytics.com/snowplow-bdp/)). +This repo contains data models which are relevant to users who already have a full Snowplow pipeline running (which can be done Open Source or via [Snowplow BDP](https://snowplow.io/snowplow-bdp/)). If you don't have a pipeline yet, you might be interested in finding out what Snowplow can do by setting up [Try Snowplow](https://try.snowplowanalytics.com/?utm_source=github&utm_medium=post&utm_campaign=try-snowplow). @@ -66,7 +66,7 @@ For detail on using the helper scripts, see the README in `.scripts/` ### Snowplow BDP -Snowplow BDP customers can configure jobs for SQL-runner in production via configuration files. [See our docs site for details on doing so](https://docs.snowplowanalytics.com/docs/modeling-your-data/configuring-and-running-data-models-via-snowplow-bdp/). The `configs/datamodeling.json` file in each model is an example configuration for the standard model. The `configs/example_with_custom.json` file is an example configuration with a customization. +Snowplow BDP customers can configure jobs for SQL-runner in production via configuration files. [See our docs site for details on doing so](https://docs.snowplow.io/docs/modeling-your-data/configuring-and-running-data-models-via-snowplow-bdp/). The `configs/datamodeling.json` file in each model is an example configuration for the standard model. The `configs/example_with_custom.json` file is an example configuration with a customization. ### Open Source @@ -103,12 +103,12 @@ limitations under the License. [license]: http://www.apache.org/licenses/LICENSE-2.0 [license-image]: http://img.shields.io/badge/license-Apache--2-blue.svg?style=flat -[tracker-classificiation]: https://docs.snowplowanalytics.com/docs/collecting-data/collecting-from-own-applications/tracker-maintenance-classification/ +[tracker-classificiation]: https://docs.snowplow.io/docs/collecting-data/collecting-from-own-applications/tracker-maintenance-classification/ [actively-maintained]: https://img.shields.io/static/v1?style=flat&label=Snowplow&message=Actively%20Maintained&color=6638b8&labelColor=9ba0aa&logo=data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAMAAAAoLQ9TAAAAeFBMVEVMaXGXANeYANeXANZbAJmXANeUANSQAM+XANeMAMpaAJhZAJeZANiXANaXANaOAM2WANVnAKWXANZ9ALtmAKVaAJmXANZaAJlXAJZdAJxaAJlZAJdbAJlbAJmQAM+UANKZANhhAJ+EAL+BAL9oAKZnAKVjAKF1ALNBd8J1AAAAKHRSTlMAa1hWXyteBTQJIEwRgUh2JjJon21wcBgNfmc+JlOBQjwezWF2l5dXzkW3/wAAAHpJREFUeNokhQOCA1EAxTL85hi7dXv/E5YPCYBq5DeN4pcqV1XbtW/xTVMIMAZE0cBHEaZhBmIQwCFofeprPUHqjmD/+7peztd62dWQRkvrQayXkn01f/gWp2CrxfjY7rcZ5V7DEMDQgmEozFpZqLUYDsNwOqbnMLwPAJEwCopZxKttAAAAAElFTkSuQmCC -[tracker-docs]: https://docs.snowplowanalytics.com/docs/collecting-data/collecting-from-own-applications/ -[docs-what-is-dm]: https://docs.snowplowanalytics.com/docs/modeling-your-data/what-is-data-modeling/ -[docs-data-models]: https://docs.snowplowanalytics.com/docs/modeling-your-data/ +[tracker-docs]: https://docs.snowplow.io/docs/collecting-data/collecting-from-own-applications/ +[docs-what-is-dm]: https://docs.snowplow.io/docs/modeling-your-data/what-is-data-modeling/ +[docs-data-models]: https://docs.snowplow.io/docs/modeling-your-data/ [sql-runner]: https://github.com/snowplow/sql-runner [sql-runner-github]: https://github.com/snowplow/sql-runner/releases/ diff --git a/mobile/v1/bigquery/README.md b/mobile/v1/bigquery/README.md index 9d6ab683..7f8fe920 100644 --- a/mobile/v1/bigquery/README.md +++ b/mobile/v1/bigquery/README.md @@ -8,7 +8,7 @@ To customise the model, we recommend following the guidance found in the README ### Prerequisites -[SQL-runner](https://github.com/snowplow/sql-runner) must be installed, and a dataset of mobile events from either the Snowplow [iOS tracker](https://docs.snowplowanalytics.com/docs/collecting-data/collecting-from-own-applications/objective-c-tracker/) or [Android tracker](https://docs.snowplowanalytics.com/docs/collecting-data/collecting-from-own-applications/android-tracker/) must be available in the database. The session context and screen view events most both be enabled for the mobile model to run. +[SQL-runner](https://github.com/snowplow/sql-runner) must be installed, and a dataset of mobile events from either the Snowplow [iOS tracker](https://docs.snowplow.io/docs/collecting-data/collecting-from-own-applications/objective-c-tracker/) or [Android tracker](https://docs.snowplow.io/docs/collecting-data/collecting-from-own-applications/android-tracker/) must be available in the database. The session context and screen view events most both be enabled for the mobile model to run. ### Configuration @@ -120,7 +120,7 @@ The `{{.scratch_schema}}.mobile_events_this_run` table contains all events relev If there is a requirement that a custom module consumes data _more frequently than the screen views module for example_, the `{{.scratch_schema}}.mobile_events_this_run` table may be used for this purpose. -The `{{.scratch_schema}}.mobile_events_staged` table is incrementally updated to contain all events relevant to any run of the base module _since the last time the sessions module consumed it_ (ie since the last time the `99-sessions-complete.yml.tmpl` has run). This allows one to run the base module more frequently than the subsequent modules (if, for example, a custom module reads from events_this_run). +The `{{.scratch_schema}}.mobile_events_staged` table is incrementally updated to contain all events relevant to any run of the base module _since the last time the sessions module consumed it_ (ie since the last time the `99-sessions-complete.yml.tmpl` has run). This allows one to run the base module more frequently than the subsequent modules (if, for example, a custom module reads from events_this_run). Detail on configuring the base module's playbook can be found [in the relevant playbook directory's README](sql-runner/playbooks/standard/01-base). @@ -214,7 +214,7 @@ Detail on configuring the users module's playbook can be found [in the relevant While the model is configured by default to run the entire way through, i.e. from the base module through to the users module, it is possible to run each module independently. For instance one could run the screen views module hourly while only running the sessions module daily. To do so you should run hourly all modules up to and including the desired module i.e. the base and screen view modules. The sessions module can then be run on a daily schedule. A few points to note: -- It is only when the sessions module is run that the `{{.scratch_schema}}.mobile_events_staged` is truncated. As a result, the hourly runs of the screen views module will both process new events data as well as re-process data stored in `mobile_events_staged` since the last time the sessions module ran. +- It is only when the sessions module is run that the `{{.scratch_schema}}.mobile_events_staged` is truncated. As a result, the hourly runs of the screen views module will both process new events data as well as re-process data stored in `mobile_events_staged` since the last time the sessions module ran. - Prior to running sessions module ensure that all input modules have been run i.e. base, screen views and _any enabled optional modules_. This ensures all the inputs are up to date and in-sync. ### Incomplete Runs @@ -222,7 +222,7 @@ While the model is configured by default to run the entire way through, i.e. fro It is not a requirement to run every module. For example you may decide you do not need sessions or users data and only want screen view data. To do so: - Set `stage_next` to `False` and `:ends_run:` to true in the screen views module. See the [README](sql-runner/playbooks/02-screen-views) for more details. -- Run all modules up to and including the screen views module. +- Run all modules up to and including the screen views module. - Ensure that the sessions 'complete' playbook, `99-sessions-complete.yml.tmpl`, is the last step in the run. This playbook includes the truncation of the `mobile_events_staged` table. Without this truncation _each subsequent run will re-process data severely impacting performance._ ## A note on duplicates diff --git a/mobile/v1/redshift/README.md b/mobile/v1/redshift/README.md index 9d381ec0..6e7733d4 100644 --- a/mobile/v1/redshift/README.md +++ b/mobile/v1/redshift/README.md @@ -8,7 +8,7 @@ To customise the model, we recommend following the guidance found in the README ### Prerequisites -[SQL-runner](https://github.com/snowplow/sql-runner) must be installed, and a dataset of mobile events from either the Snowplow [iOS tracker](https://docs.snowplowanalytics.com/docs/collecting-data/collecting-from-own-applications/objective-c-tracker/) or [Android tracker](https://docs.snowplowanalytics.com/docs/collecting-data/collecting-from-own-applications/android-tracker/) must be available in the database. The session context and screen view events most both be enabled for the mobile model to run. +[SQL-runner](https://github.com/snowplow/sql-runner) must be installed, and a dataset of mobile events from either the Snowplow [iOS tracker](https://docs.snowplow.io/docs/collecting-data/collecting-from-own-applications/objective-c-tracker/) or [Android tracker](https://docs.snowplow.io/docs/collecting-data/collecting-from-own-applications/android-tracker/) must be available in the database. The session context and screen view events most both be enabled for the mobile model to run. ### Configuration @@ -122,7 +122,7 @@ The `{{.scratch_schema}}.mobile_events_this_run` table contains all events relev If there is a requirement that a custom module consumes data _more frequently than the screen views module for example_, the `{{.scratch_schema}}.mobile_events_this_run` table may be used for this purpose. -The `{{.scratch_schema}}.mobile_events_staged` table is incrementally updated to contain all events relevant to any run of the base module _since the last time the sessions module consumed it_ (ie since the last time the `99-sessions-complete.yml.tmpl` has run). This allows one to run the base module more frequently than the subsequent modules (if, for example, a custom module reads from events_this_run). +The `{{.scratch_schema}}.mobile_events_staged` table is incrementally updated to contain all events relevant to any run of the base module _since the last time the sessions module consumed it_ (ie since the last time the `99-sessions-complete.yml.tmpl` has run). This allows one to run the base module more frequently than the subsequent modules (if, for example, a custom module reads from events_this_run). Detail on configuring the base module's playbook can be found [in the relevant playbook directory's README](sql-runner/playbooks/standard/01-base). @@ -216,7 +216,7 @@ Detail on configuring the users module's playbook can be found [in the relevant While the model is configured by default to run the entire way through, i.e. from the base module through to the users module, it is possible to run each module independently. For instance one could run the screen views module hourly while only running the sessions module daily. To do so you should run hourly all modules up to and including the desired module i.e. the base and screen view modules. The sessions module can then be run on a daily schedule. A few points to note: -- It is only when the sessions module is run that the `{{.scratch_schema}}.mobile_events_staged` is truncated. As a result, the hourly runs of the screen views module will both process new events data as well as re-process data stored in `mobile_events_staged` since the last time the sessions module ran. +- It is only when the sessions module is run that the `{{.scratch_schema}}.mobile_events_staged` is truncated. As a result, the hourly runs of the screen views module will both process new events data as well as re-process data stored in `mobile_events_staged` since the last time the sessions module ran. - Prior to running sessions module ensure that all input modules have been run i.e. base, screen views and _any enabled optional modules_. This ensures all the inputs are up to date and in-sync. ### Incomplete Runs @@ -224,7 +224,7 @@ While the model is configured by default to run the entire way through, i.e. fro It is not a requirement to run every module. For example you may decide you do not need sessions or users data and only want screen view data. To do so: - Set `stage_next` to `False` and `:ends_run:` to true in the screen views module. See the [README](sql-runner/playbooks/02-screen-views) for more details. -- Run all modules up to and including the screen views module. +- Run all modules up to and including the screen views module. - Ensure that the sessions 'complete' playbook, `99-sessions-complete.yml.tmpl`, is the last step in the run. This playbook includes the truncation of the `mobile_events_staged` table. Without this truncation _each subsequent run will re-process data severely impacting performance._ ## A note on duplicates diff --git a/mobile/v1/snowflake/README.md b/mobile/v1/snowflake/README.md index faf3fac9..2cb37aa7 100644 --- a/mobile/v1/snowflake/README.md +++ b/mobile/v1/snowflake/README.md @@ -8,7 +8,7 @@ To customise the model, we recommend following the guidance found in the README ### Prerequisites -[SQL-runner 0.9.3](https://github.com/snowplow/sql-runner) or later must be installed, and a dataset of mobile events from either the Snowplow [iOS tracker](https://docs.snowplowanalytics.com/docs/collecting-data/collecting-from-own-applications/objective-c-tracker/) or [Android tracker](https://docs.snowplowanalytics.com/docs/collecting-data/collecting-from-own-applications/android-tracker/) must be available in the database. The session context and screen view events most both be enabled for the mobile model to run. +[SQL-runner 0.9.3](https://github.com/snowplow/sql-runner) or later must be installed, and a dataset of mobile events from either the Snowplow [iOS tracker](https://docs.snowplow.io/docs/collecting-data/collecting-from-own-applications/objective-c-tracker/) or [Android tracker](https://docs.snowplow.io/docs/collecting-data/collecting-from-own-applications/android-tracker/) must be available in the database. The session context and screen view events most both be enabled for the mobile model to run. ### Configuration @@ -120,7 +120,7 @@ The `{{.scratch_schema}}.mobile_events_this_run` table contains all events relev If there is a requirement that a custom module consumes data _more frequently than the screen views module for example_, the `{{.scratch_schema}}.mobile_events_this_run` table may be used for this purpose. -The `{{.scratch_schema}}.mobile_events_staged` table is incrementally updated to contain all events relevant to any run of the base module _since the last time the sessions module consumed it_ (ie since the last time the `99-sessions-complete.yml.tmpl` has run). This allows one to run the base module more frequently than the subsequent modules (if, for example, a custom module reads from events_this_run). +The `{{.scratch_schema}}.mobile_events_staged` table is incrementally updated to contain all events relevant to any run of the base module _since the last time the sessions module consumed it_ (ie since the last time the `99-sessions-complete.yml.tmpl` has run). This allows one to run the base module more frequently than the subsequent modules (if, for example, a custom module reads from events_this_run). Detail on configuring the base module's playbook can be found [in the relevant playbook directory's README](sql-runner/playbooks/standard/01-base). @@ -214,7 +214,7 @@ Detail on configuring the users module's playbook can be found [in the relevant While the model is configured by default to run the entire way through, i.e. from the base module through to the users module, it is possible to run each module independently. For instance one could run the screen views module hourly while only running the sessions module daily. To do so you should run hourly all modules up to and including the desired module i.e. the base and screen view modules. The sessions module can then be run on a daily schedule. A few points to note: -- It is only when the sessions module is run that the `{{.scratch_schema}}.mobile_events_staged` is truncated. As a result, the hourly runs of the screen views module will both process new events data as well as re-process data stored in `mobile_events_staged` since the last time the sessions module ran. +- It is only when the sessions module is run that the `{{.scratch_schema}}.mobile_events_staged` is truncated. As a result, the hourly runs of the screen views module will both process new events data as well as re-process data stored in `mobile_events_staged` since the last time the sessions module ran. - Prior to running sessions module ensure that all input modules have been run i.e. base, screen views and _any enabled optional modules_. This ensures all the inputs are up to date and in-sync. ### Incomplete Runs @@ -222,7 +222,7 @@ While the model is configured by default to run the entire way through, i.e. fro It is not a requirement to run every module. For example you may decide you do not need sessions or users data and only want screen view data. To do so: - Set `stage_next` to `False` and `:ends_run:` to true in the screen views module. See the [README](sql-runner/playbooks/02-screen-views) for more details. -- Run all modules up to and including the screen views module. +- Run all modules up to and including the screen views module. - Ensure that the sessions 'complete' playbook, `99-sessions-complete.yml.tmpl`, is the last step in the run. This playbook includes the truncation of the `mobile_events_staged` table. Without this truncation _each subsequent run will re-process data severely impacting performance._ ## A note on duplicates diff --git a/web/v1/bigquery/README.md b/web/v1/bigquery/README.md index c87a3bd3..e7559d70 100644 --- a/web/v1/bigquery/README.md +++ b/web/v1/bigquery/README.md @@ -8,7 +8,7 @@ To customise the model, we recommend following the guidance found in the README ### Prerequisites -[SQL-runner](https://github.com/snowplow/sql-runner) must be installed, and a dataset of web events from the [Snowplow Javascript tracker](https://docs.snowplowanalytics.com/docs/collecting-data/collecting-from-own-applications/javascript-tracker/) must be available in the database. +[SQL-runner](https://github.com/snowplow/sql-runner) must be installed, and a dataset of web events from the [Snowplow Javascript tracker](https://docs.snowplow.io/docs/collecting-data/collecting-from-own-applications/javascript-trackers/javascript-tracker/) must be available in the database. ### Configuration diff --git a/web/v1/redshift/CHANGELOG b/web/v1/redshift/CHANGELOG index b72fab85..4e0947ee 100644 --- a/web/v1/redshift/CHANGELOG +++ b/web/v1/redshift/CHANGELOG @@ -1,3 +1,7 @@ +Version 1.3.1 (2022-09-02) +-------------------------- +Redshift Web: load_tstamp missing from table definition (#135) + Version 1.3.0 (2022-06-07) -------------------------- Redshift web: Change SORTKEY encoding to RAW (#129) (thanks @mark-walle!) diff --git a/web/v1/redshift/README.md b/web/v1/redshift/README.md index 067bd43d..e88f2374 100644 --- a/web/v1/redshift/README.md +++ b/web/v1/redshift/README.md @@ -8,7 +8,7 @@ To customise the model, we recommend following the guidance found in the README ### Prerequisites -[SQL-runner](https://github.com/snowplow/sql-runner) must be installed, and a dataset of web events from the [Snowplow Javascript tracker](https://docs.snowplowanalytics.com/docs/collecting-data/collecting-from-own-applications/javascript-tracker/) must be available in the database. +[SQL-runner](https://github.com/snowplow/sql-runner) must be installed, and a dataset of web events from the [Snowplow Javascript tracker](https://docs.snowplow.io/docs/collecting-data/collecting-from-own-applications/javascript-trackers/javascript-tracker/) must be available in the database. ### Configuration diff --git a/web/v1/redshift/sql-runner/playbooks/standard/00-setup/00-setup-metadata.yml.tmpl b/web/v1/redshift/sql-runner/playbooks/standard/00-setup/00-setup-metadata.yml.tmpl index aade872c..112ec753 100644 --- a/web/v1/redshift/sql-runner/playbooks/standard/00-setup/00-setup-metadata.yml.tmpl +++ b/web/v1/redshift/sql-runner/playbooks/standard/00-setup/00-setup-metadata.yml.tmpl @@ -8,7 +8,7 @@ :password: :ssl: :variables: - :model_version: redshift/web/1.3.0 + :model_version: redshift/web/1.3.1 :scratch_schema: scratch :output_schema: derived :entropy: "" diff --git a/web/v1/redshift/sql-runner/playbooks/standard/00-setup/99-metadata-complete.yml.tmpl b/web/v1/redshift/sql-runner/playbooks/standard/00-setup/99-metadata-complete.yml.tmpl index eb50423c..32490406 100644 --- a/web/v1/redshift/sql-runner/playbooks/standard/00-setup/99-metadata-complete.yml.tmpl +++ b/web/v1/redshift/sql-runner/playbooks/standard/00-setup/99-metadata-complete.yml.tmpl @@ -8,7 +8,7 @@ :password: :ssl: :variables: - :model_version: redshift/web/1.3.0 + :model_version: redshift/web/1.3.1 :scratch_schema: scratch :output_schema: derived :entropy: "" diff --git a/web/v1/redshift/sql-runner/playbooks/standard/00-setup/XX-destroy-metadata.yml.tmpl b/web/v1/redshift/sql-runner/playbooks/standard/00-setup/XX-destroy-metadata.yml.tmpl index 9a2720e7..ecf6f2db 100644 --- a/web/v1/redshift/sql-runner/playbooks/standard/00-setup/XX-destroy-metadata.yml.tmpl +++ b/web/v1/redshift/sql-runner/playbooks/standard/00-setup/XX-destroy-metadata.yml.tmpl @@ -8,7 +8,7 @@ :password: :ssl: :variables: - :model_version: redshift/web/1.3.0 + :model_version: redshift/web/1.3.1 :scratch_schema: scratch :output_schema: derived :entropy: "" diff --git a/web/v1/redshift/sql-runner/playbooks/standard/01-base/01-base-main.yml.tmpl b/web/v1/redshift/sql-runner/playbooks/standard/01-base/01-base-main.yml.tmpl index fd7540a2..1498ec03 100644 --- a/web/v1/redshift/sql-runner/playbooks/standard/01-base/01-base-main.yml.tmpl +++ b/web/v1/redshift/sql-runner/playbooks/standard/01-base/01-base-main.yml.tmpl @@ -8,7 +8,7 @@ :password: :ssl: :variables: - :model_version: redshift/web/1.3.0 + :model_version: redshift/web/1.3.1 :input_schema: atomic :scratch_schema: scratch :output_schema: derived diff --git a/web/v1/redshift/sql-runner/playbooks/standard/01-base/99-base-complete.yml.tmpl b/web/v1/redshift/sql-runner/playbooks/standard/01-base/99-base-complete.yml.tmpl index 289c52fb..10b68a28 100644 --- a/web/v1/redshift/sql-runner/playbooks/standard/01-base/99-base-complete.yml.tmpl +++ b/web/v1/redshift/sql-runner/playbooks/standard/01-base/99-base-complete.yml.tmpl @@ -8,7 +8,7 @@ :password: :ssl: :variables: - :model_version: redshift/web/1.3.0 + :model_version: redshift/web/1.3.1 :scratch_schema: scratch :output_schema: derived :entropy: "" diff --git a/web/v1/redshift/sql-runner/playbooks/standard/01-base/XX-destroy-base.yml.tmpl b/web/v1/redshift/sql-runner/playbooks/standard/01-base/XX-destroy-base.yml.tmpl index 7e51bf02..849fb8a2 100644 --- a/web/v1/redshift/sql-runner/playbooks/standard/01-base/XX-destroy-base.yml.tmpl +++ b/web/v1/redshift/sql-runner/playbooks/standard/01-base/XX-destroy-base.yml.tmpl @@ -8,7 +8,7 @@ :password: :ssl: :variables: - :model_version: redshift/web/1.3.0 + :model_version: redshift/web/1.3.1 :scratch_schema: scratch :output_schema: derived :entropy: "" diff --git a/web/v1/redshift/sql-runner/playbooks/standard/02-page-views/01-page-views-main.yml.tmpl b/web/v1/redshift/sql-runner/playbooks/standard/02-page-views/01-page-views-main.yml.tmpl index 3a72ab6c..5d5358ea 100644 --- a/web/v1/redshift/sql-runner/playbooks/standard/02-page-views/01-page-views-main.yml.tmpl +++ b/web/v1/redshift/sql-runner/playbooks/standard/02-page-views/01-page-views-main.yml.tmpl @@ -8,7 +8,7 @@ :password: :ssl: :variables: - :model_version: redshift/web/1.3.0 + :model_version: redshift/web/1.3.1 :input_schema: atomic :scratch_schema: scratch :output_schema: derived diff --git a/web/v1/redshift/sql-runner/playbooks/standard/02-page-views/99-page-views-complete.yml.tmpl b/web/v1/redshift/sql-runner/playbooks/standard/02-page-views/99-page-views-complete.yml.tmpl index c6683ccb..30a708db 100644 --- a/web/v1/redshift/sql-runner/playbooks/standard/02-page-views/99-page-views-complete.yml.tmpl +++ b/web/v1/redshift/sql-runner/playbooks/standard/02-page-views/99-page-views-complete.yml.tmpl @@ -8,7 +8,7 @@ :password: :ssl: :variables: - :model_version: redshift/web/1.3.0 + :model_version: redshift/web/1.3.1 :scratch_schema: scratch :output_schema: derived :entropy: "" diff --git a/web/v1/redshift/sql-runner/playbooks/standard/02-page-views/XX-destroy-page-views.yml.tmpl b/web/v1/redshift/sql-runner/playbooks/standard/02-page-views/XX-destroy-page-views.yml.tmpl index 68a82468..8aa24b60 100644 --- a/web/v1/redshift/sql-runner/playbooks/standard/02-page-views/XX-destroy-page-views.yml.tmpl +++ b/web/v1/redshift/sql-runner/playbooks/standard/02-page-views/XX-destroy-page-views.yml.tmpl @@ -8,7 +8,7 @@ :password: :ssl: :variables: - :model_version: redshift/web/1.3.0 + :model_version: redshift/web/1.3.1 :scratch_schema: scratch :output_schema: derived :entropy: "" diff --git a/web/v1/redshift/sql-runner/playbooks/standard/03-sessions/01-sessions-main.yml.tmpl b/web/v1/redshift/sql-runner/playbooks/standard/03-sessions/01-sessions-main.yml.tmpl index 57524ea9..5b1b9cd1 100644 --- a/web/v1/redshift/sql-runner/playbooks/standard/03-sessions/01-sessions-main.yml.tmpl +++ b/web/v1/redshift/sql-runner/playbooks/standard/03-sessions/01-sessions-main.yml.tmpl @@ -8,7 +8,7 @@ :password: :ssl: :variables: - :model_version: redshift/web/1.3.0 + :model_version: redshift/web/1.3.1 :scratch_schema: scratch :output_schema: derived :entropy: "" diff --git a/web/v1/redshift/sql-runner/playbooks/standard/03-sessions/99-sessions-complete.yml.tmpl b/web/v1/redshift/sql-runner/playbooks/standard/03-sessions/99-sessions-complete.yml.tmpl index 63349656..96f69202 100644 --- a/web/v1/redshift/sql-runner/playbooks/standard/03-sessions/99-sessions-complete.yml.tmpl +++ b/web/v1/redshift/sql-runner/playbooks/standard/03-sessions/99-sessions-complete.yml.tmpl @@ -8,7 +8,7 @@ :password: :ssl: :variables: - :model_version: redshift/web/1.3.0 + :model_version: redshift/web/1.3.1 :scratch_schema: scratch :output_schema: derived :entropy: "" diff --git a/web/v1/redshift/sql-runner/playbooks/standard/03-sessions/XX-destroy-sessions.yml.tmpl b/web/v1/redshift/sql-runner/playbooks/standard/03-sessions/XX-destroy-sessions.yml.tmpl index 5dd78f3c..7fd9159f 100644 --- a/web/v1/redshift/sql-runner/playbooks/standard/03-sessions/XX-destroy-sessions.yml.tmpl +++ b/web/v1/redshift/sql-runner/playbooks/standard/03-sessions/XX-destroy-sessions.yml.tmpl @@ -8,7 +8,7 @@ :password: :ssl: :variables: - :model_version: redshift/web/1.3.0 + :model_version: redshift/web/1.3.1 :scratch_schema: scratch :output_schema: derived :entropy: "" diff --git a/web/v1/redshift/sql-runner/playbooks/standard/04-users/01-users-main.yml.tmpl b/web/v1/redshift/sql-runner/playbooks/standard/04-users/01-users-main.yml.tmpl index d5dc5b2b..e5f76c23 100644 --- a/web/v1/redshift/sql-runner/playbooks/standard/04-users/01-users-main.yml.tmpl +++ b/web/v1/redshift/sql-runner/playbooks/standard/04-users/01-users-main.yml.tmpl @@ -8,7 +8,7 @@ :password: :ssl: :variables: - :model_version: redshift/web/1.3.0 + :model_version: redshift/web/1.3.1 :scratch_schema: scratch :output_schema: derived :entropy: "" diff --git a/web/v1/redshift/sql-runner/playbooks/standard/04-users/99-users-complete.yml.tmpl b/web/v1/redshift/sql-runner/playbooks/standard/04-users/99-users-complete.yml.tmpl index afb897c1..414d162a 100644 --- a/web/v1/redshift/sql-runner/playbooks/standard/04-users/99-users-complete.yml.tmpl +++ b/web/v1/redshift/sql-runner/playbooks/standard/04-users/99-users-complete.yml.tmpl @@ -8,7 +8,7 @@ :password: :ssl: :variables: - :model_version: redshift/web/1.3.0 + :model_version: redshift/web/1.3.1 :scratch_schema: scratch :output_schema: derived :entropy: "" diff --git a/web/v1/redshift/sql-runner/playbooks/standard/04-users/XX-destroy-users.yml.tmpl b/web/v1/redshift/sql-runner/playbooks/standard/04-users/XX-destroy-users.yml.tmpl index efb4139d..dfbb2d16 100644 --- a/web/v1/redshift/sql-runner/playbooks/standard/04-users/XX-destroy-users.yml.tmpl +++ b/web/v1/redshift/sql-runner/playbooks/standard/04-users/XX-destroy-users.yml.tmpl @@ -8,7 +8,7 @@ :password: :ssl: :variables: - :model_version: redshift/web/1.3.0 + :model_version: redshift/web/1.3.1 :scratch_schema: scratch :output_schema: derived :entropy: "" diff --git a/web/v1/snowflake/README.md b/web/v1/snowflake/README.md index f1a7b6a1..1a507746 100644 --- a/web/v1/snowflake/README.md +++ b/web/v1/snowflake/README.md @@ -8,7 +8,7 @@ To customise the model, we recommend following the guidance found in the [README ### Prerequisites -[SQL-runner](https://github.com/snowplow/sql-runner) must be installed, and a dataset of web events from the [Snowplow Javascript tracker](https://docs.snowplowanalytics.com/docs/collecting-data/collecting-from-own-applications/javascript-tracker/) must be available in the database. +[SQL-runner](https://github.com/snowplow/sql-runner) must be installed, and a dataset of web events from the [Snowplow Javascript tracker](https://docs.snowplow.io/docs/collecting-data/collecting-from-own-applications/javascript-trackers/javascript-tracker/) must be available in the database. **Note:** For the Snowflake web model, SQL Runner v0.9.3 or above is required.