+1 , We are in need to find a reference code where we can take decision
transparently just where "where conditions" which backend-data-store the
results should be served.
On Friday 27 November 2015 05:51 PM, Rajat Venkatesh wrote:
Hi Sarnath,
We are building something similar at Qubole. The difference is that our
customers store their cubes and vies in a relational database - usually AWS
Redshift. So their application continues to refer to tables in Hive but a
cube or a view is used to answer the query if possible. The queries are
routed to the right data store.
All this is built on top of the calcite optimizer and we also have JDBC
access using Avatica. We don't have a JDBC server yet but a fat jar.
Seems like you working on something similar. I'll gladly exchange notes. We
are planning to open source it as well. So if you wish to use it as a
platform for your experiments, I can help with that as well.
On Thursday 26 November 2015, Sarnath <[email protected]> wrote:
Hi Julian,
Thanks for the details and thanks a lot for your time. It looks pretty
simple. We will explore more and get back here if we cannot resolve it
through the docs.
Again, thanks a lot for your time and your help.
Best,
Sarnath
