livepeer / livepeer/livepeer-data-mcp
[Feedback] :pencil2: correction — retention cohort join with date range conditions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Feedback (correction)
Question: retention cohort join with date range conditions
Tool: query
Notes
ClickHouse rejects dateDiff() and inequality expressions in JOIN ON clauses (e.g. event_date > signup_date, dateDiff(...) BETWEEN 0 AND 6). Must move those conditions to WHERE or use maxIf() in SELECT instead. CASE/multiIf with integer comparisons also works for segment labeling but watch for 0-indexed cohort_id producing unexpected labels.
Feedback ID: 1b719860-e122-4aa0-aa50-626c3bb9d6e1 | Recorded at 2026-03-09T20:54:44.821Z
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
The feedback concerns the query tool and ClickHouse retention-cohort joins; no file, test, or implementation entry point is named. Start by locating the query handler and any retention-cohort examples, then reproduce the reported date-range JOIN behavior and inspect cohort_id labeling. The issue does not define a repository change or acceptance test, so confirm the expected behavior before editing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100