That's partly why I wanted to create a tool to query various databases (NoSQL ones or files too) with SQL. We're still in an early stage with OctoSQL regarding the variety of databases, but take a look if that sound appreciable to you: https://github.com/cube2222/octosql/
btw, not being critical of your project, just trying to understand it.
There's a great paper on that: "One SQL to Rule Them All", check it out.
We also want to scale well from single computer one-of data exploration queries, to full blown clustered long-term stateful stream processing.
The point is to provide a well thought out SQL interface to as many data sources as possible, and like drill does, push down as much computation as possible.
We actually learned about drill only after creating OctoSQL, but that's another story. (We're definitely less mature currently and support fewer datasources)
I believe there is a similar effort going on in the Flink project. They're slowly merging in work from the Blink project to provide a unified SQL paradigm (batch + stream).
We're basically aiming for a middle ground between Flink, Presto and Drill.