OctoSQL[0] or DuckDB[1] will most likely be much simpler, while going through 10 GB of JSON in a couple seconds at most. Disclaimer: author of OctoSQL [0]: https://github.com/cube2222/octosql. - Source: Hacker News / about 1 year ago

This is really cool! With their Postgres scanner[0] you can now easily query multiple datasources using SQL and join between them (i.e. Postgres table with JSON file). Something I strived to build with OctoSQL[1] before. It's amazing to see how quickly DuckDB is adding new features. Not a huge fan of C++, which is right now used for authoring extensions, it'd be really cool if somebody implemented a Rust extension... - Source: Hacker News / over 1 year ago

Congrats on the Show HN! It's great to see more tools in this area (querying data from various sources in-place) and the Lambda use case is a really cool idea! I've recently done a bunch of benchmarking, including ClickHouse Local and the usage was straightforward, with everything working as it's supposed to. Just to comment on the performance area though, one area I think ClickHouse could still possibly improve... - Source: Hacker News / over 1 year ago

SPyQL is really cool and its design is very smart, with it being able to leverage normal Python functions! As far as similar tools go, I recommend taking a look at DataFusion[0], dsq[1], and OctoSQL[2]. DataFusion is a very (very very) fast command-line SQL engine but with limited support for data formats. Dsq is based on SQLite which means it has to load data into SQLite first, but then gives you the whole breath... - Source: Hacker News / over 1 year ago

To add somewhat of a counterpoint to the other response, I've tried the Steampipe CSV plugin and got 50x slower performance vs OctoSQL[0], which is itself 5x slower than something like DataFusion[1]. The CSV plugin doesn't contact any external API's so it should be a good benchmark of the plugin architecture, though it might just not be optimized yet. That said, I don't imagine this ever being a bottleneck for the... - Source: Hacker News / over 1 year ago

Example notebooks are included in the repo and can be previewed using nbviewer:. Source: over 1 year ago

Nbviewer (https://nbviewer.org/): very easy to use for smaller jupyter notebook that does not require heavy rendering. Source: over 1 year ago

Nbconvert renders everything exactly as it looks in your notebook app into a read-only HTML version and is what GitHub uses for notebooks. Interactive plots from Bokeh, Holoviews, etc can still work if you trust the JS, and since editing notebooks while showing them during a meeting usually doesn't go well, read-only is probably good enough (eager to hear feedback on this point though). The nice thing is that... Source: over 1 year ago

Just as a heads up, I used plotly to generate a lot of the charts, so you'll need to view it from an nbviewer like nbviewer.org. Source: about 2 years ago

I used a lot of plotly not knowing that Github wouldn't show it, so you'll need notebook viewer like nbviewer.org to see some of the charts. Source: about 2 years ago