4 ms·
Yeah It’s more like a spec, they expect you to write the query optimizer, analyzer basically a new query engine. They offered a document based “reference” imple
by whoevercares 6y ago
Yeah It’s more like a spec, they expect you to write the query optimizer, analyzer basically a new query engine. They offered a document based “reference” implementation on Kotlin though so I think expert could follow it.
Point is AWS might not make up its mind yet on whether this does more harm to their DB business or not
- gavinray 6y agoAhh. I guess for SQL you could just pass the queries through, and for NoSQL engines try to convert the AST format. When I was researching this area, it seems like Apache Calcite is the way to go, and already does this though? It lets you use standard SQL and has adapters which translate from the abstract query AST to the particular implementation. https://calcite.apache.org/docs/adapter.html https://calcite.apache.org/docs/adapter.html You can query anything with this, exactly the same way. It's kind of wild I've never heard it talked about tbh. I went looking for solutions to multi-datastore querying when I fiddled with a business intelligence side project. Pretty useless to only be able to query one type of data, and too time consuming to implement individual mappings. Apache Calcite and Metabase Query Language (quite the exact usecase there for Metabase, haha) were the only things I could find.