Skip to content

Commit

Permalink
Merge pull request #13 from fivetran/MagicBot_01f5094dee
Browse files Browse the repository at this point in the history
[MagicBot] Bumping package version
  • Loading branch information
fivetran-joemarkiewicz authored Jul 28, 2021
2 parents c102fae + 0576549 commit 2f7c34d
Show file tree
Hide file tree
Showing 5 changed files with 42 additions and 26 deletions.
19 changes: 19 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
[![Apache License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0) ![dbt logo and version](https://img.shields.io/static/v1?logo=dbt&label=dbt-version&message=0.20.x&color=orange)
# LinkedIn Ad Analytics ([docs](https://fivetran-dbt-linkedin.netlify.app/#!/overview))

This package models LinkedIn Ad Analytics data from [Fivetran's connector](https://fivetran.com/docs/applications/linkedin-ads). It uses data in the format described by [this ERD](https://fivetran.com/docs/applications/linkedin-ads#schemainformation).
Expand All @@ -18,6 +19,14 @@ This package contains transformation models, designed to work simultaneously wit
## Installation Instructions
Check [dbt Hub](https://hub.getdbt.com/) for the latest installation instructions, or [read the dbt docs](https://docs.getdbt.com/docs/package-management) for more information on installing packages.

Include in your `packages.yml`

```yaml
packages:
- package: fivetran/linkedin
version: [">=0.3.0", "<0.4.0"]
```
## Configuration
By default, this package will look for your LinkedIn Ad Analytics data in the `linkedin_ads` schema of your [target database](https://docs.getdbt.com/docs/running-a-dbt-project/using-the-command-line-interface/configure-your-profile). If this is not where your LinkedIn Ad Analytics data is, please add the following configuration to your `dbt_project.yml` file:

Expand Down Expand Up @@ -81,6 +90,16 @@ on the best workflow for contributing to a package.
## Database Support
This package has been tested on BigQuery, Snowflake, Redshift, Postgres, and Databricks.

### Databricks Dispatch Configuration
dbt `v0.20.0` introduced a new project-level dispatch configuration that enables an "override" setting for all dispatched macros. If you are using a Databricks destination with this package you will need to add the below (or a variation of the below) dispatch configuration within your `dbt_project.yml`. This is required in order for the package to accurately search for macros within the `dbt-labs/spark_utils` then the `dbt-labs/dbt_utils` packages respectively.
```yml
# dbt_project.yml
dispatch:
- macro_namespace: dbt_utils
search_order: ['spark_utils', 'dbt_utils']
```

## Resources:
- Provide [feedback](https://www.surveymonkey.com/r/DQ7K7WW) on our existing dbt packages or what you'd like to see next
- Have questions, feedback, or need help? Book a time during our office hours [using Calendly](https://calendly.com/fivetran-solutions-team/fivetran-solutions-team-office-hours) or email us at [email protected]
Expand Down
30 changes: 12 additions & 18 deletions dbt_project.yml
Original file line number Diff line number Diff line change
@@ -1,22 +1,16 @@

name: 'linkedin'
version: '0.3.1'
version: '0.3.0'
config-version: 2
require-dbt-version: [">=0.18.0", "<0.20.0"]

require-dbt-version: [">=0.20.0"]
vars:
linkedin:
ad_analytics_by_creative: "{{ ref('stg_linkedin__ad_analytics_by_creative') }}"
creative_history: "{{ ref('stg_linkedin__creative_history') }}"
campaign_history: "{{ ref('stg_linkedin__campaign_history') }}"
campaign_group_history: "{{ ref('stg_linkedin__campaign_group_history') }}"
account_history: "{{ ref('stg_linkedin__account_history') }}"
dbt_utils_dispatch_list: ['spark_utils', 'fivetran_utils']
fivetran_utils_dispatch_list: ['spark_utils']

linkedin__passthrough_metrics: []

linkedin:
ad_analytics_by_creative: "{{ ref('stg_linkedin__ad_analytics_by_creative') }}"
creative_history: "{{ ref('stg_linkedin__creative_history') }}"
campaign_history: "{{ ref('stg_linkedin__campaign_history') }}"
campaign_group_history: "{{ ref('stg_linkedin__campaign_group_history') }}"
account_history: "{{ ref('stg_linkedin__account_history') }}"
linkedin__passthrough_metrics: []
models:
linkedin:
+materialized: table
+schema: linkedin
linkedin:
+materialized: table
+schema: linkedin
7 changes: 5 additions & 2 deletions integration_tests/dbt_project.yml
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
name: 'linkedin_integration_tests'
version: '0.3.1'
version: '0.3.0'
profile: 'integration_tests'
config-version: 2

Expand Down Expand Up @@ -36,4 +36,7 @@ seeds:
linkedin_creative_history_data:
+column_types:
created_time: timestamp
last_modified_time: timestamp
last_modified_time: timestamp
dispatch:
- macro_namespace: dbt_utils
search_order: ['spark_utils', 'dbt_utils']
6 changes: 3 additions & 3 deletions integration_tests/requirements.txt
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
dbt==0.19.1
dbt-spark==0.19.1
dbt-spark[PyHive]==0.19.1
dbt==0.20.0
dbt-spark==0.20.0
dbt-spark[PyHive]==0.20.0
6 changes: 3 additions & 3 deletions packages.yml
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
packages:
- package: fivetran/linkedin_source
version: [">=0.2.0", "<0.3.0"]
packages:
- package: fivetran/linkedin_source
version: [">=0.3.0", "<0.4.0"]

0 comments on commit 2f7c34d

Please sign in to comment.