livepeer / livepeer/livepeer-data-mcp
[Feedback] :pencil2: correction — Scope cohort retention D1/D3/D7/D14
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
## Feedback (correction)
**Question:** Scope cohort retention D1/D3/D7/D14
**Tool:** `query`
**Dataset:** `scope_cloud_events`
### Notes
Scope retention was initially measured as dateDiff(first_event, last_event) which inflates early cohorts who simply span more days. Correct approach: explicit day-window joins using maxIf(1, dateDiff = N) to check for actual return events in each window. Also: ClickHouse rejects inequality conditions (> and <) directly in JOIN ON clauses — must use WHERE clause after the join instead.
---
_Feedback ID: `9ef811d5-bd97-4b86-ab1d-7484c17a8292` | Recorded at 2026-03-09T20:54:39.495Z_
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the query for the scope_cloud_events dataset and review how cohort retention is calculated. Replace the dateDiff(first_event, last_event) span check with explicit D1/D3/D7/D14 return-event windows using maxIf(1, dateDiff = N), and keep inequality conditions out of JOIN ON clauses by applying them in WHERE; done means the early-cohort inflation is removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse
- Domain
- data, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100