3 ms·
It certainly seems more lightweight and modular, but I'm curious if you see this overlapping with Presto at all, in terms of product fit, scale/performance, etc
by WaxProlix 4y ago
It certainly seems more lightweight and modular, but I'm curious if you see this overlapping with Presto at all, in terms of product fit, scale/performance, etc.
I'll almost certainly use this to pull parquet, orc, and csv data into postgres at some point in the next month or two, so thanks.
- cube2222 4y agoThe main difference in product fit is that OctoSQL is single-machine-only and I have no plans for distributed execution. I'm not sure about the performance of Presto, but I'd expect OctoSQL to be of fairly similar speed for complex operations/data types (operating on strings, objects, running some functions on them) and slower for vectorizable arithmetics (avg of a column of floats in a parquet file). Other than that, OctoSQL should be much easier to write plugins for, much easier to use, and even though there's no plugin for it yet, it should have much better support for streaming inputs (i.e. Kafka).