3 ms·
If I understand correctly: 1. you define activities, each with an associated SQL query eg customer opened support ticket: SELECT * FROM tickets WHERE customer
by mariushn 6y ago
If I understand correctly:
1. you define activities, each with an associated SQL query
eg customer opened support ticket: SELECT * FROM tickets WHERE customer_id=$customer_id
2. users use Narrator UI to build a report, similar to Looker
3. Narrator creates a table for that report in the same db and populates it with data, based on 1.
4. Narrator maintains all the reports tables (updates, deletes when report is deleted)
?
- cedricd 6y agoYes, that's basically it. 2. The report (we call it Dataset) you build with the Narrator UI is a table that you can aggregate different ways, plot, and export (including writing back to the warehouse as a materialized view) 3. done optionally as part of 2 4. Yes, we keep anything written back to the warehouse up to date. You can control the cadence. Because of 4. we work well with BI tools like Looker. Once you have the data you want just point Looker to the right table in the warehouse.
- mariushn 6y agoThanks. Interesting approach!