Add consolidated results tables

Open
#2,036 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
data, databases

Research direction

The issue names AnalysisPeriod-level tables and the existing _<analysis_period> tables; start by tracing how those result tables are produced. Compare the consolidated-table behavior with BigQuery wildcard and Looker’s experimentation/analysis_statistics constraints; done means queries can span experiments and answer cross-experiment questions.

Written by the indexing model from the issue text.

Description

We would like to query across experiment results to be able to answer questions such as "which experiments moved retention?". Currently, that's not possible to do. It's also not possible to use BQ's query wildcard functionality to do this, as our results use views and tables. Also, it's not possible to use Looker's experimentation/analysis_statistics explore because that can query only a single slug.

Each AnalysisPeriod-level table would effectively be a union of existing <slug>_<analysis_period> tables.

┆Issue is synchronized with this Jira Task

Dominant language
Python
Stars
26
Forks
14
Avg merge
19h 55m
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla/jetstream

All issues in mozilla/jetstream

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.