You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: dbt_project.yml
+28-28Lines changed: 28 additions & 28 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
-
name: 'overbase_firebase'
2
-
version: '0.9.10'
1
+
name: 'ta_firebase'
2
+
version: '0.9.13'
3
3
config-version: 2
4
4
5
5
# This setting configures which "profile" dbt uses for this project.
@@ -18,23 +18,23 @@ clean-targets: # directories to be removed by `dbt clean`
18
18
- "dbt_packages"
19
19
20
20
models:
21
-
overbase_firebase:
21
+
ta_firebase:
22
22
# Applies to all files under models/example/
23
23
materialized: table
24
-
schema: overbase
24
+
schema: ta_firebase
25
25
+persist_docs:
26
26
relation: true
27
27
columns: true
28
28
29
29
seeds:
30
-
overbase_firebase:
31
-
schema: overbase
30
+
ta_firebase:
31
+
schema: ta
32
32
33
33
vars:
34
-
overbase_firebase:
35
-
"OVERBASE:DONT_CARE": "MAKE_YAML_WORK"# optional
36
-
"OVERBASE:SOURCES_READY": false
37
-
# "OVERBASE:SOURCES":
34
+
ta_firebase:
35
+
"TA:DONT_CARE": "MAKE_YAML_WORK"# optional
36
+
"TA:SOURCES_READY": false
37
+
# "TA:SOURCES":
38
38
# - {project_id: watermark-maker,
39
39
# analytics_dataset_id: analytics_150733022,
40
40
# events_table: events_*,
@@ -50,24 +50,24 @@ vars:
50
50
# don't define variables here, because if they aren't overwritten in the client yml, then they will resolve to "None".
51
51
# Instead, use them in the package where you need them with them with the appropriate default value
52
52
# Furthermore, whatever we use in sources.yml, we can't define in this package's dbt_project.yml, or else they won't be able to be overwritten by the client
53
-
# Any mandatory variables you want to be enforced should go into overbase_mandatory_vars.sql
53
+
# Any mandatory variables you want to be enforced should go into ta_mandatory_vars.sql
54
54
# The comments liste here is just for our sanity & easier c/p in client configs
55
-
# "OVERBASE:FIREBASE_ANALYTICS_CUSTOM_INSTALL_EVENT": "" # optional e.g. attributed_first_open
56
-
# "OVERBASE:CUSTOM_PLATFORM_PREPROCESSOR": "IF(app_info.version LIKE '%nexus', 'nexus', platform)"
# "OVERBASE:FIREBASE_CRASHLYTICS_FULL_REFRESH_END_DATE": "20219-01-05" #optional, if you want to make
63
-
# "OVERBASE:OB_DIMENSION_TO_EXCLUDE_IN_ROLLUPS": # optional, what built-in OB dimensions to exclude from bubbling up in the rollups (& save the row count)
55
+
# "TA:FIREBASE_ANALYTICS_CUSTOM_INSTALL_EVENT": "" # optional e.g. attributed_first_open
56
+
# "TA:CUSTOM_PLATFORM_PREPROCESSOR": "IF(app_info.version LIKE '%nexus', 'nexus', platform)"
# additional_filter: error_type = 'FATAL' AND custom_keys.call_state = 'duringCall'
118
-
# "OVERBASE:CUSTOM_APP_HEALTH_METRICS": # TODO later on, forward to the BI tool as the semantic layer
118
+
# "TA:CUSTOM_APP_HEALTH_METRICS": # TODO later on, forward to the BI tool as the semantic layer
119
119
# NOT IMPLEMENTED ATM
120
120
# - name: signup_ratio
121
121
# type: ratio
122
122
# numerator_agg: SUM(##)
123
-
# numerator_filter : event_name LIKE '%view_shown' AND event_parameters.view_name_string = 'signup step 1' AND event_parameters.view_type_string = 'ob-forced-null'
123
+
# numerator_filter : event_name LIKE '%view_show' AND event_parameters.view_name_string = 'signup step 1' AND event_parameters.view_type_string = 'ta-forced-null'
124
124
# denominator_agg: SUM(##)
125
-
# denominator_filter: event_name LIKE '%view_shown' AND event_parameters.view_name_string = 'signup step 5' AND event_parameters.view_type_string = 'ob-forced-null'
125
+
# denominator_filter: event_name LIKE '%view_show' AND event_parameters.view_name_string = 'signup step 5' AND event_parameters.view_type_string = 'ta-forced-null'
0 commit comments