Live data from Hacker News

Apache Superset

superset.apache.org

141–150 of 201 posts

Re: Apache Superset

#141
post #64

Had a very good experience with Superset. Superset allowed us to replace Tableau and not looking back Took me a while figure out how to embed it into my app using Superset Embedded SDK. Superset Embedded SDK - "Embedded SDK allows you to embed dashboards from Superset into your own app, using your app's authentication. Embedding is done by inserting an iframe, containing a Superset page, into the host application." h…

I’d like to see these types of apps start offering SVG embedding of things like graphs. Frames are such a pain.

Bokeh is an option in the frontend-viz space that puts out pretty solid SVG for statically-rendered charts, while also having the option of more Tableau-like interactive functionality with input fields, dynamic filters, etc. Might be a decent option for you?

Their interactive "embedded-mode" avoids iframes too... but it's built with web components, so you wind up in shadow-DOM hell if you want to do anything dynamic on the view's contents.

Re: Apache Superset

#142
post #7
post #2

> Superset is fast, lightweight, intuitive, and loaded with options that make it easy for users of all skill sets to explore and visualize their data, from simple line charts to highly detailed geospatial charts. I tried Superset a few years back, and maybe it's changed since then, but intuitive is about the last thing I'd use to describe it. Things which I could figure out in a few minutes on any other BI tool liter…

I also found Superset unintuitive to use and setup as well. I settled on standing up Metabase because it was so simple to get started with trying it since it can be launched as a single jar. The business users loved it and so did I and administration with a Postgres backend instead of the internal h2 database was a breeze.

I had the same experience. Featurewise Superset looked better, but after wasting a couple of hours trying to install it, I just gave up.

Instead I installed Metabase in 5 minutes tops: spin ec2 instance, whether and java -jar . I've never looked back.

The only thing that turns me off I'd that it's implemented in an obscure language. At one time I wanted to add some custom postprocessing to an api (given an sql query, get some python/pandas postproc command from a sql comment and execute it in the returned table), but the used language is just not for me (some lisp dialect)

Re: Apache Superset

#144

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?

Mhmm this gives me an idea.. what if I could "group" metabase sql queries by "similarity" (either of results or of the query itself)

Another option could be to use LLM to summarize, tag and group queries for better discoverability.

Re: Apache Superset

#145

Earlier quoted context omitted.

They're both washboarding apps, and while I'm sure they each have panel types the other doesn't yet support, I don't think that's intrinsic. The differentiation as I see it, is that Superset is designed to craft SQL queries and visualize the results. The query builder is probably where this shows the most. To make it more concrete -- coworkers tell me Grafana doesn't work so well with Apache Druid, while Superset sup…

*dashboarding, yikes

I thought this was some jargon I didn't know haha.

Re: Apache Superset

#146

anyone knows how does it compare to Looker?

No built-in thick semantic layer, compared to Looker. I wrote about Superset's semantic layer here: https://preset.io/blog/understanding-superset-semantic-layer... One popular option is to use dbt or Cube for the semantic layer and pair with Superset: https://preset.io/blog/announcing-presets-ui-integration-wit... and https://preset.io/blog/open-source-looker-cube-superset/

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

Re: Apache Superset

#147
love superset, but one thing that I would love to see is to make it easier for dashboards/charts to use a dynamic table that the user can select.

we have multiple tenants + developer instances of our warehouse. to reuse the same dashboard in this setup we need to create at least 3 virtual datasets, plus wrangle a bunch of boiler plate jinja.

Re: Apache Superset

#148
Used Superset back in 2016 and 2020; both time chose Metabase for our clients' BI dashboard and Superset for our internal dashboard. Superset is nice, easy to modify and extend but not user friendly as Redash or Metabase. But after the author launched Preset, it seems to have improved much with the company effort. It looks like to me the best way for OSS to advance is to have a company dedicated to improve it.

Re: Apache Superset

#149

Earlier quoted context omitted.

How do you deal with data visibility and permissions? I mean, most tables have data that should only be seen by a specific user or group ID, and that layer is usually handled by the application. It would be awesome to expose the power of Superset for users, but I imagine creating the security layer would be a pain.

You can use row-level security, or specify RBAC with pretty much any SQL query.

[deleted]

Re: Apache Superset

#150

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.

Post reply on HN