Closed
Bug 1355988
Opened 9 years ago
Closed 9 years ago
Provide search cohort churn data via csv
Categories
(Data Platform and Tools :: General, enhancement, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mpressman, Assigned: amiyaguchi)
Details
Attachments
(1 file)
We need the following:
channel,
geo,
is_funnelcake,
acquisition_period,
start_version,
sync_usage,
current_version,
current_week,
source,
medium,
campaign,
content,
distribution_id,
default_search_engine,
locale,
is_active,
n_profiles,
usage_hours,
sum_squared_usage_hours
If you can output that to:
s3://net-mozaws-prod-us-west2-pipeline-analysis/amiyaguchi/churn_csv
Thanks!
| Assignee | ||
Updated•9 years ago
|
Assignee: nobody → amiyaguchi
| Assignee | ||
Updated•9 years ago
|
Points: --- → 1
Priority: -- → P1
| Assignee | ||
Updated•9 years ago
|
Summary: Please and thank you for providing the search cohort churn data in csv → Provide search cohort churn data via csv
| Assignee | ||
Comment 1•9 years ago
|
||
I think this should be seen as a stopgap measure while other solutions to import this dataset into vertica are worked out. There have been some good alternatives proposed for syncing and moving this data, including querying directly from Presto/Athena.
| Assignee | ||
Comment 2•9 years ago
|
||
| Assignee | ||
Comment 3•9 years ago
|
||
This data should be generated alongside the other csv files. The output csv files are gzip compressed in s3://net-mozaws-prod-us-west2-pipeline-analysis/amiyaguchi/churn_csv/week_start={week start date}.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•3 years ago
|
Component: Datasets: General → General
You need to log in
before you can comment on or make changes to this bug.
Description
•