191–200 of 201 posts
Can this work to give end-users/customers the ability to create their own reports/charts, respecting data access visibility etc? I am in need of a "dashboarding" feature in our SaaS, but it seems there's a gap between PowerBI/Tableau/Metabase/Superset and various charting libraries. The former are too much "turn key" and the latter require a ton of work to setup all the chart-building UI and features...
Earlier quoted context omitted.
The lack of a semantic layer and join limitations are what made me pass on superset, but that was a couple years ago so maybe those features have been added. I built my own semantic layer instead. I use this in production in my company but obviously use at your own risk as it's a one-man show. https://github.com/totalhack/zillion
This looks interesting for me, but I'd really like more detail about the architecture and deployment in the docs. There is this: > A final SQL query against the combined data from the DataSource Layer > The Combined Layer is just another SQL database (in-memory SQLite by default) that is used to tie the datasource data together and apply a few additional features such as rollups, row filters, row limits, sorting, piv…
It first runs one or more queries against your DataSources in a drill-across query fashion. You can think of DataSources as one or more completely separate databases. You could have one mysql, one postgresql, one duckdb etc all in the same Warehouse (not saying this is common in production, just an example). Within those DataSource queries it's also joining all needed tables together for you, i.e. joining multiple tables in each database to meet your required grain.
It then takes the results of all those queries and combines that data in another layer which is currently an in-memory sqlite database. The purpose of that layer is joining the data for presentation as well as applying some additional features like rollups, technicals, formula fields, etc.
I'm not familiar with what superset does under the hood or exposes as an API so I don't know how to compare it, if there is some similar backend piece. But I suspect no part of superset is quite the same as this, based on what its front end can do.
Happy to answer any other questions you have.
Has anyone tried both this and Metabase? I've used Metabase in a few projects and I find it very nice. This seems more powerful, perhaps? Is it worth it for BI on small datasets?
Reposting from a comment of mine about 60 days ago: I recently ran a little shootout between Superset, Metabase, and Lightdash — all open source with hosted options. All have nontrivial weaknesses but I ended up picking Lightdash. Superset is the best of them at data visualization but I honestly found it almost useless for self-serve BI by business users if you have existing star schema. This issue on how to do joins…
(one of the maintainers of Lightdash) You touched on some of our most interesting problems here! Would be especially interested to hear about what you liked / didn't like about symmetric aggregates in Looker and how you find dev with YAML. If you have an idea of how you'd like these to look in Lightdash, the team would be really open to making that a reality.
For pivoting in the backend, this is coming! Issue here: https://github.com/lightdash/lightdash/issues/2907
We use metabase heavily at work. However where it seems like all these tools fall down is organization around the hundreds of dashboards and questions. I wish it had like a built wiki or something to build out more navigation. Anyone know of any good ways to do that?
100% agree. One thing that helps is hooking metabase up to its own database and building queries on your queries, e.g.: select * from report_card where dataset_query ilike '%' || {{query}} || '%' (You can also join in metadata like the author, when it was last ran, etc.) We also try really hard to keep the Collection directory structure clean and consistent. But it's still really hard.
Earlier quoted context omitted.
Maxime, the original author of Airflow/Superset, is also the CEO of Preset (where I work), so he/we are still working on Superset every day :)
Oh that's awesome! Must be awesome to work on that. We've been using Airflow in production for 6 years at this point with various clients and it's been great, and we're trying to sell people on Superset now as well.
Earlier quoted context omitted.
Oh that's awesome! Must be awesome to work on that. We've been using Airflow in production for 6 years at this point with various clients and it's been great, and we're trying to sell people on Superset now as well.
[flagged]
If you truly want me to answer, and you're only posting here because you can't reply to old threads, let me know and I'll send you my personal email and we can engage there.
Earlier quoted context omitted.
Oh that's awesome! Must be awesome to work on that. We've been using Airflow in production for 6 years at this point with various clients and it's been great, and we're trying to sell people on Superset now as well.
[flagged]
There's another problem: you've been posting about nothing but this one topic for months. That's not what HN is for. I know the topic is important and I'm sure your views are sincere, but we still have to preserve this site for its intended purpose. Using HN primarily for political battle and similar conflicts is against HN's rules, not because those conflicts don't matter (of course they matter, more than basically everything on HN), but because if we don't have such a rule, they will take over the site completely, and then HN won't be HN any more.
If you'd please review https://news.ycombinator.com/newsguidelines.html and stick to the rules when posting here, we'd appreciate it.
Earlier quoted context omitted.
[flagged]
Obviously you can't attack another user like this on HN, so please don't. There's another problem: you've been posting about nothing but this one topic for months. That's not what HN is for. I know the topic is important and I'm sure your views are sincere, but we still have to preserve this site for its intended purpose. Using HN primarily for political battle and similar conflicts is against HN's rules, not because…