As I commented on a recent similar discussion, these tools can't be used for update or insert. As useful as querying might be, it's terribly misleading to claim to "run SQL" if you can't change the data, since that's such a critical part of an SQL database.
Question: I've built something that supports full CRUD, and queries that span multiple data sources with optimization and pushdown What kind of headline would make you want to read/try such a thing? (I'm planning on announcing it + releasing code on HN but have never done so before)
Run SQL on CSV, Parquet, JSON, Arrow, Unix Pipes and Google Sheet
61–64 of 64 posts
Re: Run SQL on CSV, Parquet, JSON, Arrow, Unix Pipes and Google Sheet
#62Earlier quoted context omitted.
Ah nice, thank you for sharing that. I hadn’t seen it before, and congrats on beating out Spark that hard, I hope it continues to improve! As an aside, maybe it would make sense to publish a new blog post somewhere so that the top hit on Google for “DataFusion benchmark” isn’t that post I linked.
Haha, yeah, we should definitely put a little bit more efforts into SEO :) Everyone is so focused on the hard-core engineering at the moment. I think Matthew from the community is actually working on a new comprehensive benchmark for us at the moment, which I hope will be published soon.
Re: Run SQL on CSV, Parquet, JSON, Arrow, Unix Pipes and Google Sheet
#63This is cool...Totally reminded me about several tools pop up on HN every now and then in the past for similar task so i did a quick search: clickhouse-local - https://news.ycombinator.com/item?id=22457767 q - https://news.ycombinator.com/item?id=27423276 textql - https://news.ycombinator.com/item?id=16781294 simpql- https://news.ycombinator.com/item?id=25791207 We need a benchmark i think..;)
Re: Run SQL on CSV, Parquet, JSON, Arrow, Unix Pipes and Google Sheet
#64Earlier quoted context omitted.
Maybe in your database. Do you have any validation of that claim in a larger context?
Purely the power law. That would be an interesting thing to figure out though. Maybe a github crawl. EDIT: I stand corrected based on github code files (which might better represent application CRUD queries versus use by analysts, more thought required!) SELECT: 7.3M code results [0] INSERT: 8.9M code results [1] UPDATE: 5.5M code results [2] DELETE: 5.0M code results [3] [0] https://github.com/search?q=select++exten…
So even a read-heavy application could have more writes than reads due to caching.