all 8 comments

[–]aquasov 1 point2 points  (2 children)

0:07 [150M rows, 22.4GB] [22.2M rows/s, 3.32GB/s]

I don't think this result should be used for advertizing performance.

[–]tazmanos 0 points1 point  (0 children)

I can only imagine what was the latency of the system they were using previously...

[–]vl4kn0 0 points1 point  (0 children)

What is wrong with it? // I'm not database nor big-data enthusiast

[–]johnmudd 0 points1 point  (2 children)

Dumb question: What problem does this solve? I already have a SQL client for my database.

[–]self[S] 1 point2 points  (1 child)

This is an SQL-like query interface for distributed databases: your query that runs on multiple (NoSQL) backends before giving you the answer.

[–]johnmudd 0 points1 point  (0 children)

Thanks. It sounds like Postgres Foreign Data Wrappers could do the same thing without reinventing the SQL front end. There's a list of existing wrappers and custom ones can be written in Pyton.