livepeer / livepeer/livepeer-data-mcp
[Feedback] :thumbsup: positive — cohort member lists and retention vs non-cohort users
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
## Feedback (positive)
**Question:** cohort member lists and retention vs non-cohort users
**Tool:** `query`
**Dataset:** `dbt.cohorts, dbt.cohort_members`
### Notes
Cohort membership data lives in dbt.cohorts and dbt.cohort_members — NOT in the semantic schema and NOT discoverable via list_datasets. Must use SHOW TABLES FROM dbt to find them. Schema: dbt.cohorts (cohort_id Int, cohort_name String, track String, start_date Date, end_date Date). dbt.cohort_members (cohort_id Int, track String, user_email String). Join keys: user_email → scope_cloud_events.user_email, user_email → posthog_events.daydream_user_email. These tables should be added to list_datasets / semantic schema.
---
_Feedback ID: `35de64b9-e307-41ab-a53b-735617b428f7` | Recorded at 2026-03-09T21:54:06.705Z_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by inspecting the implementation of list_datasets and the semantic schema, then use SHOW TABLES FROM dbt to verify the cohort tables and their columns. The work is done when dbt.cohorts and dbt.cohort_members are discoverable through both interfaces with the documented user_email joins represented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100