Hi JiaTao,
Thanks for your valuable information. :-)
We plan to parse SQL (ShardingSphere and Calcite) twice at the first step for
federated SQL query (It includes @Jason Chen's case).
Twice-parsing is not a big issue for query efficiency (as you said) though,
we still want to know whether there is any possibility to bypass the SQL
parsing from Calcite?
Best wishes,
Trista
Juan Pan (Trista)
Senior DBA & PMC of Apache ShardingSphere
E-mail: [email protected]
On 11/22/2020 16:39，JiaTao Tao<[email protected]> wrote：
I think you are talking about query federation, yes, it's a good case for
Caclite.
Regards!
Aron Tao
Jason Chen <[email protected]> 于2020年11月4日周三 上午8:06写道：
Hey,
I am Jason Chen from Shopify Data Science and Engineering team. I have a
few questions regarding the Apache Calcite, and I am not sure if the Apache
Calcite fits our use cases. Feel free to point me to the correct email or
Slack channel if this email is not the correct one for asking questions.
We are exploring the approaches to do mixed querying across multiple
storage resources. One use cases is doing the “JOIN” in query time of query
results from both Druid and BigTable/Spanner. Is this a good use case for
Apache Calcite?
Thank you for any help!
Regards,
Jason Chen
Jason (Jianbin) Chen
Senior Data Developer
p: +1 2066608351 | e: [email protected]
a: 234 Laurier Ave W Ottawa, ON K1N 5X8
