Implement materialized managed views for Revenue analytics
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 222
Description
Feature request
Rather than creating in-memory views for Revenue Analytics, let's instead store them in the database. We'll eventually want them to be materialized, but that's something we can work on as a follow-up since this will be trivial
Contributor guide
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 Revenue Analytics' in-memory view creation and the database persistence entry point. Replace the in-memory storage with database-backed views, and verify that Revenue Analytics reads the stored views; materialization is explicitly a follow-up rather than part of this issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- analytics, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100